Add a workflow that rebuilds a published release and attests it - #26
Merged
Conversation
The release build is deterministic, so the tagged source rebuilds the published archive byte for byte. This makes provenance recoverable: a release can be re-attested at any time without touching the artifact anyone already downloaded. The rebuild is gated on the checksum published with the release. If the bytes do not reproduce, the job fails and signs nothing, because an attestation is only worth making when the claim inside it is true. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The release build is deterministic: a fresh checkout of a release tag rebuilds the published archive byte for byte. That makes provenance recoverable — a release can be re-attested at any time without touching the artifact anyone already downloaded.
The job rebuilds the tagged source, then compares the result against the
.sha256published with the release. If the bytes do not reproduce, it fails and signs nothing. An attestation says this workflow built these exact bytes from this exact source, and that is only worth claiming when it is true.Action pins match
release.ymlas of this branch point (checkoutv7.0.0,attestv4.2.2).🤖 Generated with Claude Code