fix: publish signed release artifacts (cosign v3 bundle format) - #72
Merged
Merged
Conversation
MPV
force-pushed
the
claude/release-signing-bundle
branch
2 times, most recently
from
August 8, 2026 21:16
f688b8f to
2c4737e
Compare
MPV
changed the title
v0.3.0 tagged and released but shipped no artifacts: GoReleaser aborted at the
signing step because cosign v3 (installed by cosign-installer) removed
sign-blob's --output-signature/--output-certificate flags in favour of a single
Sigstore bundle, so the old config failed with "create bundle file: open : no
such file or directory".
Migrate the checksum `signs` block to the bundle format: emit one
`checksums.txt.sigstore.json` via `--bundle=${signature}`, matching Sigstore's
own .goreleaser.yml and GoReleaser's cosign v3 guidance. cosign stays current
(no version pin); `docker_signs` (`cosign sign --yes`) is unchanged. With this,
the release publishes the binaries, checksums, SBOMs, image, and signatures.
Typed `fix:` intentionally so it cuts a release (v0.3.1) and gets the first
signed artifacts out — v0.3.0 published none. Verification lives in
CONTRIBUTING.md.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016RJcNXwJdwhtEgsfLfYKtv
MPV
force-pushed
the
claude/release-signing-bundle
branch
from
August 8, 2026 21:20
2c4737e to
03f9480
Compare
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
2 participants
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
Repairs release signing so a release actually ships artifacts — and does it as a releasable
fix:so merging this cuts v0.3.1 and gets the first signed binaries out.v0.3.0tagged/released but published nothing because signing aborted.Root cause
cosign-installerpulls cosign v3, which removedsign-blob's--output-signature/--output-certificateflags in favour of a single Sigstore bundle. The old config aborted:Fix
One
checksums.txt.sigstore.jsonbundle (sig + cert + Rekor proof), covering every binary viachecksums.txt. Verified against Sigstore's own.goreleaser.ymland GoReleaser's cosign v3 guidance (#6195). cosign stays current — no pin.docker_signs(cosign sign --yes) is unchanged (image signing wasn't affected). Verify instructions added toCONTRIBUTING.md.On the
fix:typeStrictly a
.goreleaser.yamlchange isci:/build:, butv0.3.0's release is defective from a user's view (no downloadable/signed artifacts). Typing thisfix:is the honest, practical framing — the user-facing effect is "signed binaries now publish" — and it's what makes merging this produce the release you want.Result
Merge this → release-please opens a v0.3.1 Release PR → merge that → GoReleaser runs the fixed config → first fully signed release (binaries +
.sigstore.json+ image + SBOMs).Supersedes
#70 (pin cosign) and #71 (hold signing) — both can be closed.
🤖 Generated with Claude Code
https://claude.ai/code/session_016RJcNXwJdwhtEgsfLfYKtv