Repository navigation
Generate release manifests from verified candidate artifacts - #415
Merged
Merged
Conversation
This was referenced Nov 9, 2026
9 of 10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preparing a release currently means copying run IDs and commits into three platform entries by hand. Rerunning a selected workflow can also replace name-based artifacts behind those run IDs.
Add a CLI that takes an explicit full candidate SHA, expected root version, Desktop run and Daemon run. Verify successful same-candidate workflows, all six unexpired Release staging artifacts, component/source/version/configuration metadata, Linux tarball checksums and shared core provenance. Cached SDK producer revisions remain valid only with matching core source and root version. Downloaded ZIP hashes are checked against GitHub digests when available.
Generate the existing manifest structure with artifact IDs/checksums, plus a companion evidence record containing run attempts, artifact identities/expiry and SDK producer/archive digests. Update all three staging consumers to download pinned IDs; legacy manifests retain name-based selection. Existing candidate outputs are never overwritten. Add the staging suite to Repository checks and update the runbook with the command and expiry/recovery procedure.
Validation: 41 staging/manifest tests and 19 release tests pass, including consumer preparation for all three platforms, deterministic output, immutable output files, pagination, cached-SDK identity and rejection of missing/mixed/expired/development/checksum-invalid inputs. Core/contract boundaries, changed workflow YAML and diff checks pass. A live read-only check rejected successful CI runs without Release artifacts; the real download helper read a small existing core-selection artifact and matched its ZIP hash to GitHub’s digest.
Continues #121 and #122. Full staging with a generated candidate remains to be validated through the next actual release; no extra release builds or publication were dispatched for this PR.