release candidates: draft assets are read by their attachment uuid (the tag URL is 404 for drafts: the record job could not merge SHA256SUMS); the installers are scanned with the private terms in their build jobs, so the record job needs no apt tools (it spent 5 minutes installing them)
This commit is contained in:
parent
cdaecc2afb
commit
6873f2cc68
5 changed files with 34 additions and 23 deletions
|
|
@ -56,7 +56,7 @@ tested twice: every push to main is already a release candidate.
|
|||
cached, so only changed crates compile);
|
||||
- `windows`: the NSIS installer, silent per-user install, self-test, uninstall, the Node prompt smoke, privacy scan.
|
||||
|
||||
When all are green, the `record` job scans the installers with the private terms (secret `FORBIDDEN_TERMS`), builds
|
||||
The build jobs scan the installers with the private terms (secret `FORBIDDEN_TERMS`). When all are green, the `record` job builds
|
||||
the 6-run acceptance matrix, and stores everything as the **draft release `rc-<full sha>`** on git.crt.fyi:
|
||||
installers, `SHA256SUMS`, the acceptance run files, `storebound_<version>_acceptance.md` and `green.json` (sha,
|
||||
version, CLI key, run link, every file's SHA-256). `green.json` is uploaded last: a candidate without it is not
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue