fix(release): migrate cosign signing to v3 bundle format (BUG-2091)#925
Merged
Conversation
The cosign-installer action bump (v3.10.1 → v4.1.2) pulled the cosign binary from v2.x to v3.0.6. cosign v3 defaults --new-bundle-format=true for sign-blob and drops the separate --output-certificate/--output-signature outputs, breaking GoReleaser's signs block: Error: signing dist/checksums.txt: create bundle file: open : no such file or directory Caught by the v0.10.0-rc.1 release run. Migrate to the official cosign-v3 path (https://goreleaser.com/blog/cosign-v3/): emit a single Sigstore bundle checksums.txt.sigstore.json via --bundle, replacing the .pem/.sig pair. Verify with `cosign verify-blob --bundle checksums.txt.sigstore.json`. Also refreshes the stale verify comment (was checksums.txt.cosign.bundle). Claude-Session: https://claude.ai/code/session_015yuBJQYfDj95cgX3DaD8SF
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.
What
The v0.10.0-rc.1 release failed at Run GoReleaser because the cosign-installer bump (v3.10.1 → v4.1.2) pulled the cosign binary from v2.x to v3.0.6. cosign v3 defaults
--new-bundle-format=trueforsign-bloband removes the separate--output-certificate/--output-signatureoutputs:Fix
Migrate
.goreleaser.yamlsigns block to the official cosign-v3 path: emit a single Sigstore bundlechecksums.txt.sigstore.jsonvia--bundle, replacing the.pem+.sigpair. Also refreshes the stale verify comment.Artifact-shape change (intentional)
checksums.txt.pem+checksums.txt.sig→checksums.txt.sigstore.jsoncosign verify-blob --bundle checksums.txt.sigstore.json --certificate-identity-regexp ... checksums.txtValidation
Regular CI can't exercise the signing path (tag-triggered only) — this is validated by re-cutting v0.10.0-rc.2. Confirmed locally that the cosign v3
--bundlecommand is flag-valid (cosign v3.0.6, same binary the runner installs).Follow-ups (tracked on BUG-2091)
Closes BUG-2091. Supersedes stale-comment drift in TASK-1032.
https://claude.ai/code/session_015yuBJQYfDj95cgX3DaD8SF