Verify MSI SBOM attestations#87
Merged
Merged
Conversation
kans
approved these changes
May 27, 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
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 verifier is being extended to verify SPDX SBOM bundles from release asset attestations. The non-Axiomatic Windows release path already asks GoReleaser for installer SBOMs, but the Windows signing step did not require them and the release validator skipped MSI SBOM verification.
What this changes
This can land after registry API PR #153; that registry PR intentionally keeps MSI SBOMs optional during the workflow transition.
Validation: