fix: authenticate release attestation checks - #11
Merged
Conversation
What changed: - expose the existing GitHub token only to the signing and verification step - add a regression contract and refresh the source manifest Why: - gh attestation verify refuses to run in GitHub Actions without GH_TOKEN
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.
What changed
Root cause
Release run 32210878721 successfully installed Cosign, signed the candidate, created SPDX and OpenVEX attestations, and verified them with Cosign. The subsequent
gh attestation verifycommand exited with code 4 because GitHub CLI requiresGH_TOKENinside Actions.Validation
sha256:4e4776d18a92076a51c5bc92efa89e269595e47fb62ebe763910b07af829c9f4using checksum-pinned GitHub CLI v2.97.0No image/runtime, signing identity, permission, attestation, publication-order, or Cloudflare behavior changes.