fix(release): bump cosign to v2.6.3 — unblocks v0.3.0 release workflow#31
Merged
Merged
Conversation
…rify its download bundle
The v0.3.0 release run (27300066093) failed before goreleaser even
started: goreleaser-action verifies the downloaded goreleaser binary
against checksums.txt.sigstore.json, and cosign v2.4.1 cannot read the
new-style protobuf sigstore bundle goreleaser v2.16.0 publishes
('bundle does not contain cert for verification, please provide public
key'). v2.6.3 (latest v2 line) reads the new bundle format while
keeping our signs: invocation (sign-blob --output-signature
--output-certificate --yes) contract-identical.
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 v0.3.0 tag's release run (27300066093) failed before goreleaser ran:
goreleaser-actionverifies its own downloaded binary againstchecksums.txt.sigstore.json, and the pinned cosign v2.4.1 cannot read the new-style protobuf sigstore bundle that goreleaser v2.16.0 publishes:Bumping to v2.6.3 (latest v2 line) fixes bundle verification while keeping our
signs:invocation (sign-blob --output-signature --output-certificate --yes) contract-identical. Workflow-only change; the v0.3.0 tag will be re-cut on the merge commit (the failed run published no artifacts).🤖 Generated with Claude Code