fix(release): pin cosign CLI to v2.6.3; prepare v0.3.2#85
Merged
Conversation
The v0.3.1 tag build failed at the signing step: cosign-installer
fetches latest cosign by default and cosign v3 ignores
--output-signature/--output-certificate in favor of the new bundle
format ('create bundle file: open : no such file or directory'). Pin
cosign-release v2.6.3 so the .sig/.crt assets documented in
docs/verifying-releases.md keep being produced; migrate to bundles
deliberately later.
v0.3.1 is already cached by the Go module proxy, so the tag must not
move — it stays a valid module version with no release binaries.
Prepare v0.3.2 instead (content-identical plus this pipeline fix):
changelog entry + bump usage examples to @v0.3.2.
Co-Authored-By: Claude Opus 4.8 <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
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.3.1 tag build failed at signing: cosign-installer installs the latest cosign by default, and the actions-group dependabot bump moved runners onto cosign v3, which ignores
--output-signature/--output-certificate(new bundle format) and errors withcreate bundle file: open : no such file or directory. Failed run.cosign-release: v2.6.3on the installer (with a comment explaining why), keeping the.sig/.crtassets that docs/verifying-releases.md documents. Migrating to the v3 bundle format can be a deliberate follow-up.@v0.3.2example bumps.Tag v0.3.2 goes on the merge commit.
🤖 Generated with Claude Code