fix(ci): pin cosign to v2 line to unbreak release signing#39
Merged
Conversation
….pem contract The Dependabot bump of sigstore/cosign-installer to v4 started installing cosign v3, which defaults to the new bundle format: it ignores --output-signature/--output-certificate and fails with 'create bundle file: open : no such file or directory' because no --bundle path is set. Pin cosign-release to v2.6.3 to restore the signing contract documented in docs/security.md; migrating to the bundle format is a separate change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ration path Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
alxxjohn
added a commit
that referenced
this pull request
Jul 16, 2026
🤖 I have created a release *beep* *boop* --- ## [0.8.3](v0.8.2...v0.8.3) (2026-07-16) ### Bug Fixes * **ci:** pin cosign to the v2 line so release signing keeps the .sig/.pem contract ([9ee93c4](9ee93c4)) * **ci:** pin cosign to v2 line to unbreak release signing ([#39](#39)) ([218f078](218f078)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Summary
The v0.8.2 release failed at the artifact-signing step:
Root cause: Dependabot's bump of
sigstore/cosign-installerv3 → v4 started installing cosign v3, which enables the new sigstore bundle format by default. In that mode cosign ignores the--output-signature/--output-certificateflags passed by.goreleaser.yamland requires a--bundlepath it never receives, so it fails with an empty file path.Fix: pin
cosign-release: v2.6.3(the latest, still-maintained v2 release). This keeps the.sig/.pemartifact contract thatdocs/security.mddocuments for release verification, and makes the one previously floating binary in the release workflow version-pinned like everything else.Follow-up (separate PR): migrate the goreleaser
signsconfig to the cosign v3 bundle format (--bundleproducing a single.sigstore.json) and update the verification docs — that changes the artifact contract for verifiers, so it should be a deliberate, reviewed change rather than part of this unblock.After merge, re-run the v0.8.2 release workflow.
🤖 Generated with Claude Code