Repository navigation
M0.11: enforce verified deployment policy - #14
Merged
Merged
Conversation
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.
Implements M0.11 consumer-side release verification.
Changes:
scripts/verify-release.shto resolve a release tag to an immutable digest, verify the exact Sigstore/Cosign signer identity and GitHub Actions OIDC issuer, and optionally pull only after verification succeeds;Deployment verificationCI, qualifying the policy against signedv0.2.3and exercising verify-before-pull;docs/M0_11_VERIFIED_DEPLOYMENT.mdwith trust policy and acceptance criteria;The trust policy intentionally keeps exact identity matching and verifies the immutable digest rather than a mutable tag.