Send signed manifest metadata to registry#84
Merged
Conversation
ennyjfrick
approved these changes
May 26, 2026
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
2 participants
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.
Why
The registry now needs the published manifest URL and Sigstore bundle URL to verify release recordings before accepting them.
What this changes
Adds signatureBundleHref to release manifests, signs the final manifest with a Sigstore bundle, uploads the bundle with the manifest, passes the manifest URL to record-release, and blocks registry recording until release artifact verification succeeds. Adds a make verify target covering proto generation, focused Go tests, and workflow YAML parsing.
Notes
Merge along with the registry verification PR.