Repository navigation
release: from main only, tagged after its files are signed - #106
Merged
Merged
Conversation
S4 of the supply-chain plan. The release workflow no longer runs on a pushed tag: it is dispatched on main, every job of it runs only there, it names its version from the caller or today's sequence, and tags the commit once its files are signed and attested, refusing a version tagged already. The certificate then always names release.yml at main; the provenance carries which release a file is. workflows_test holds release.yml to it. Co-Authored-By: Claude Opus 5.5 (1M context) <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
1 participant
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.
S4 of the supply-chain plan (PR 13 in the table): spin-machine releases from main and nothing else.
release.yml:push: tagstrigger is gone, so a pushed tag starts nothing.refs/heads/main.git push. The globalconcurrency: releasestays.release.yml@refs/heads/main. Which release a file is comes from its provenance (externalParameters.version).workflows_test:MainOnly: [release.yml]. Planted: dropping the release job'sif:fails the test.@refs/heads/main.Nothing consumes a machine release by its signature yet. spin pins the machine by sha256, and the S4 spin PR adds the provenance check against the main identity. So no consumer breaks.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.