Repository navigation
Conversation
…elease Tag builds assembled a verified release-candidate artifact, but nothing put it on the release page, so every release needed a manual download and upload. A separate Draft release workflow now runs after a successful version-tag Build: it downloads that run's release-candidate, checks its SHA-256 list, confirms the tag still names the built commit, and uploads the files to the tag's draft release (creating the draft if needed). It never checks out or runs repository code, never publishes, and refuses a release that is already published. Build stays read-only, and the gating contract pins both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Summary
Tag builds assembled a verified
release-candidateartifact, but nothing put it on the release page. The v0.8.0 draft had 0 assets after a green build.This adds
.github/workflows/draft-release.yml. It runs onworkflow_runafter Build completes, and only for a successfulpushbuild of av*tag. It:release-candidateartifact;sha256sum --check --strict checksums-sha256.txt;It never publishes, and it refuses a release that is already published. It never checks out or runs repository code. Its only write permission is
contents: writeon this one job, from the job's short-lived token; no secrets are used.Build keeps
permissions: contents: read, and its existing "cannot publish" contract still holds. A new contract test incheck-ci-release-gating.test.mjspins the new workflow's trigger, its guards, that it has exactly one write permission, and that there is no checkout, push, publish orsecrets.use.RELEASING.md and DEVELOPMENT.md describe the new step.
Verification
node --test scripts/release/check-ci-release-gating.test.mjs: 23/23 pass.workflow_runworkflows run from the default branch, so this takes effect for tag builds after it merges.🤖 Generated with Claude Code