Repository navigation
Attest the build provenance of every release file - #5
Merged
Merged
Conversation
The release workflow's last step signs a SLSA build provenance attestation, with actions/attest, for every file in SHA256SUMS: each binary and its SBOM. It shows that this workflow built the file from the tagged commit, which a checksum published beside the file cannot. The README shows how to check one with "gh attestation verify". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6
Merged
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.
Summary
Adds signed build provenance to every release file.
actions/attestv4.2.2 signs a SLSA build provenance attestation with Sigstore for every file indist/SHA256SUMS: the six binaries and their SBOMs. Each attestation records which workflow run built the file, from which commit. GoReleaser writesSHA256SUMSafter signing and notarizing the macOS binaries, so the digests match the files people download.id-token: write(Sigstore signing) andattestations: write(storing the attestation).artifact-metadata: writeis only needed when pushing to a container registry, so it's left out.gh attestation verify ... --signer-workflow .../release.yml, which also works on a Homebrew-installedrypt.The SBOM is attested as a release file. It is not yet bound to its binary as an SBOM-type attestation; that can follow if wanted.
Testing
actionlintv1.7.12 passes on all workflows.gh attestation verify rypt-linux-amd64 --repo x6c-co/rypt-cli --signer-workflow x6c-co/rypt-cli/.github/workflows/release.ymlon a downloaded binary.🤖 Generated with Claude Code
https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6