Skip to content

fix(#8): sign with cosign --new-bundle-format #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
scttfrdmn merged 1 commit into from
Jul 20, 2026
Merged

fix(#8): sign with cosign --new-bundle-format #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,14 @@ jobs:
# short-lived Fulcio cert, signs manifest.json, and records the entry in
# Rekor. The bundle (cert + signature + log proof) is self-contained, so
# spawn verifies it offline against the sigstore trust root.
#
# --new-bundle-format emits the Sigstore protobuf bundle (the format
# sigstore-go — and thus spawn — parses). Without it, cosign writes the
# LEGACY bundle ({base64Signature,cert,rekorBundle}), which spawn's
# verifier can't load. The flag is "deprecated" only in the sense that
# it will become the sole format in a future cosign; it is required here.
COSIGN_EXPERIMENTAL=1 cosign sign-blob --yes \
--new-bundle-format \
--bundle manifest.json.sigstore.json \
manifest.json
echo "::group::manifest.json.sigstore.json"
Expand Down