Skip to content

Verify MSI SBOM attestations#87

Merged
gontzess merged 1 commit into
mainfrom
gontzess/verify-msi-sbom-attestations
May 27, 2026
Merged

Verify MSI SBOM attestations#87
gontzess merged 1 commit into
mainfrom
gontzess/verify-msi-sbom-attestations

Conversation

@gontzess
Copy link
Copy Markdown
Contributor

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

  • Requires each Windows zip and MSI artifact to have an SPDX SBOM before signing SBOM attestation bundles.
  • Fails the Windows release job if no Windows SBOM bundles are produced.
  • Verifies MSI detached signatures, provenance attestations, and SBOM attestations in the release artifact validator.

This can land after registry API PR #153; that registry PR intentionally keeps MSI SBOMs optional during the workflow transition.

Validation:

  • bash -n scripts/validate-release-artifacts.sh
  • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/release.yaml")'\n- go test ./cmd/generate-windows-manifest ./cmd/record-release ./cmd/generate-manifest ./cmd/merge-manifests\n- git diff --check

@gontzess gontzess marked this pull request as ready for review May 27, 2026 20:08
@gontzess gontzess merged commit 6892174 into main May 27, 2026
2 checks passed
@gontzess gontzess deleted the gontzess/verify-msi-sbom-attestations branch May 27, 2026 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants