Skip to content

ci(release): pin cosign to v2.4.3 (fix v0.1.0 signing)#58

Merged
001TMF merged 1 commit into
mainfrom
fix/release-cosign-bundle
Jun 15, 2026
Merged

ci(release): pin cosign to v2.4.3 (fix v0.1.0 signing)#58
001TMF merged 1 commit into
mainfrom
fix/release-cosign-bundle

Conversation

@001TMF

@001TMF 001TMF commented Jun 15, 2026

Copy link
Copy Markdown
Owner

The v0.1.0 release workflow failed at the cosign signing step — build, archives, and SBOM succeeded. The default cosign now uses the Sigstore bundle format and ignores --output-signature/--output-certificate, so goreleaser's sign-blob resolved to an empty --bundle path and errored (create bundle file: open : no such file or directory).

install.sh verifies a detached checksums.txt.sig + checksums.txt.pem, so the producer must keep emitting those. This pins cosign-release: v2.4.3 (pre-bundle-default) to realign the formats. No .goreleaser.yaml or install.sh change needed.

After merge: re-tag v0.1.0 to re-run the release.

🤖 Generated with Claude Code

The v0.1.0 release failed at signing: the cosign installed by default now
defaults to the Sigstore bundle format and ignores --output-signature /
--output-certificate, so goreleaser's sign-blob wrote an empty bundle path and
errored. install.sh verifies a detached checksums.txt.sig + .pem, so pin cosign
to v2.4.3 (pre-bundle-default) to keep the producer/consumer formats aligned.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@001TMF 001TMF merged commit 0f254a6 into main Jun 15, 2026
3 checks passed
@001TMF 001TMF deleted the fix/release-cosign-bundle branch June 15, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant