fix(release): migrate signing to cosign v3 bundle format#2
Merged
Conversation
The v0.1.0 release run failed at goreleaser setup: goreleaser-action
verifies its own pinned tool download using cosign's Sigstore-bundle
format, but cosign-installer@v3.7.0 ships cosign v2.4.x, which can't
read that bundle ("bundle does not contain cert for verification,
please provide public key").
Align with GoReleaser's canonical supply-chain example:
- release.yml: cosign-installer @v3.7.0 -> @v4.1.2 (installs cosign
v3.0.x); pin goreleaser-action @v7 -> @v7.2.2.
- .goreleaser.yml signs block: emit a single self-contained Sigstore
bundle (checksums.txt.sigstore.json) via `--bundle=${signature}`
instead of separate --output-certificate/--output-signature
(.pem/.sig) files.
- README: verify with `cosign verify-blob --bundle
checksums.txt.sigstore.json ...` (no more .sig/.pem).
Validated with `goreleaser check`. Keyless signing itself can only be
exercised in CI (needs Actions OIDC), so the re-tagged release run is
the real test.
Co-Authored-By: Claude Opus 4.8 (1M context) <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.1.0release run failed at goreleaser setup — before our own signing ran.Root cause
goreleaser/goreleaser-actionverifies its own pinned goreleaser download using cosign against the Sigstore bundle format.sigstore/cosign-installer@v3.7.0installs cosign v2.4.x, which can't parse that bundle:cosign v3 streamlined signing into a single
.sigstore.jsonbundle; verifying goreleaser's download (and producing our own signature) now requires cosign v3.Fix — align with GoReleaser's canonical supply-chain example
release.yml:cosign-installer@v3.7.0→@v4.1.2(installs cosign v3.0.x); pingoreleaser-action@v7→@v7.2.2..goreleaser.ymlsigns block → bundle format:--bundle=${signature}withsignature: "${artifact}.sigstore.json", dropping the separate--output-certificate/--output-signature(.pem/.sig).README.md: verify withcosign verify-blob --bundle checksums.txt.sigstore.json ….Validation
goreleaser checkpasses; YAML parses. Keyless signing needs Actions OIDC, so it can only be exercised in CI — the re-cutv0.1.0run is the real test.🤖 Generated with Claude Code