Repository navigation
ci: render release notes from a reviewed template (digest is known only after the build) - #8
Merged
Merged
Conversation
…before-build ordering The notes were required to contain the archive digest, which is unknown until the archive is built, so a committed note could never pass. The reviewed template now carries explicit tokens that publish fills, and refuses a template without the digest token or with an unknown token. A first template states only what the workflow itself verifies. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Fixes a design flaw found before the first dry run: publish required the notes to contain the archive SHA-256, which cannot be committed before the archive exists. The notes are now a reviewed template with explicit tokens.
🤖 Generated with Claude Code