Repository navigation
ci: attest build provenance and SBOM for releases - #46
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
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.
Releases shipped checksummed archives but no signed provenance or SBOM.
id-token: write+attestations: write(plus existingcontents: write).anchore/sbom-actionand upload it to the release.actions/attest-build-provenance) and the SBOM (actions/attest-sbom) for the four archives andchecksums.txt, using keyless Sigstore signing.RELEASING.mdverify steps andINSTALL.md/ website guide showgh attestation verify <archive> --repo vmrocha/bible-cli.Third-party actions pinned to full SHAs (
sbom-actionv0.24.3,attest-build-provenancev4.2.2,attest-sbomv4.1.0). The attestation steps only run on a tagged release, so they can't be exercised until the next tag; YAML validated locally.