ci: harden attest workflow and publish signed release assets#4
Merged
Conversation
Pin actions by commit SHA, restrict the trigger to release tags, split permissions per job, attach the tarball and its Sigstore bundle to a GitHub release, and verify the published attestation as a final job.
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.
Hardens the Attest workflow per supply-chain best practices: actions pinned by SHA, trigger narrowed to release tags, least-privilege permissions per job, no credential persistence. The signed tarball and its attestation bundle are now published as release assets, and a final job re-downloads and verifies them.