Repository navigation
A tag's run runs the strict source gates and requires green CI on the commit - #161
Merged
Merged
Conversation
…signatures or provenance do not verify, the gates CI runs on every push, before it builds a release
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.
The tag-triggered Distro run checked pins and ran the acceptance but never the strict source-signature and provenance gates, which only CI runs, and nothing tied the tag to a CI verdict. Now, before anything is built on a tag:
verify-signatures.sh --strictandverify-provenance.sh --strictrun on the fetched sources, and the run reads CI's conclusion for the tagged commit (waiting up to 40 minutes for a run still going) and refuses a commit CI did not pass or never tested. The toolchain job gainsactions: readfor that query. docs/releases.md says so.