Skip to content

ci(release): pin cosign to v2.5.2 (fix GitHub Release signing)#54

Merged
tachyon-beep merged 1 commit into
mainfrom
ci/pin-cosign
Jun 5, 2026
Merged

ci(release): pin cosign to v2.5.2 (fix GitHub Release signing)#54
tachyon-beep merged 1 commit into
mainfrom
ci/pin-cosign

Conversation

@tachyon-beep

Copy link
Copy Markdown
Collaborator

cosign-installer's resolved default moved to v3.0.6, whose sign-blob requires a bundle and breaks the --output-signature/--output-certificate flow (create bundle file: open :) — which failed the v1.0.0 GitHub Release job. PyPI publish was unaffected (loomweave + loomweave-plugin-python are live at 1.0.0).

v2.5.2 signed the last good release (Clarion v1.1.0). Pinned in both cosign-installer steps. Workflow-only change (release.yml runs on tags only).

🤖 Generated with Claude Code

The cosign-installer's resolved default moved to v3.0.6, whose `sign-blob`
requires a bundle and breaks the `--output-signature`/`--output-certificate`
flow ("create bundle file: open :") — which failed the v1.0.0 GitHub Release
job (PyPI publish was unaffected). v2.5.2 is the version that signed the last
good release (Clarion v1.1.0). Pin it in both cosign-installer steps (sign +
verify-published). Porting to cosign 3.x's bundle API is a separate follow-up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tachyon-beep tachyon-beep merged commit 5030887 into main Jun 5, 2026
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