Repository navigation
fix(release): unbreak cosign signing and OLM sync - #340
Merged
Merged
Conversation
KeiaiLab-PHIL
enabled auto-merge (squash)
October 6, 2026 02:20
cosign-installer v4 installs cosign v3, whose sign-blob defaults to the new bundle format. That mode ignores --output-signature and --output-certificate and fails without --bundle: signing out/valkey-operator-1.5.1.tgz: create bundle file: open : no such file or directory This broke "Package & sign helm chart" on v1.5.1, so no GitHub Release was cut by the workflow. Pass --new-bundle-format=false --use-signing-config=false on both sign-blob steps (chart and SBOM) so the .sig/.pem assets SECURITY.md documents are produced again. Keyless signing via Fulcio/Rekor is unchanged. sync-community-operators needs COMMUNITY_OPERATORS_PAT, which is not configured. It runs after the GitHub Release, so it can only turn a published release red. Skip its steps with a warning when the secret is empty; behavior with the secret set is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: phil <phil@keiailab.com>
eightynine01
force-pushed
the
fix/release-cosign-v3
branch
from
October 6, 2026 02:27
ccf99b2 to
ed466fd
Compare
KeiaiLab-PHIL
changed the title
Merged
KeiaiLab-PHIL
added a commit
that referenced
this pull request
Oct 6, 2026
Security release so ArtifactHub rescans the chart and image. Chart version/appVersion 1.5.3, operator image entry 1.5.3, and artifacthub.io/changes for #327 (deps + Go 1.26.8), #330 (no password hash in pod annotations), #328/#329 (supply-chain hardening), #339 (Valkey 9.1.2 default) and #340 (release workflow signing). Signed-off-by: phil <phil@keiailab.com> Co-authored-by: Claude Opus 5.5 <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
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.
cosign-installer v4 installs cosign v3, whose sign-blob defaults to
the new bundle format. That mode ignores --output-signature and
--output-certificate and fails without --bundle:
signing out/valkey-operator-1.5.1.tgz: create bundle file:
open : no such file or directory
This broke "Package & sign helm chart" on v1.5.1, so no GitHub
Release was cut by the workflow. Pass --new-bundle-format=false
--use-signing-config=false on both sign-blob steps (chart and
SBOM) so the .sig/.pem assets SECURITY.md documents are produced
again. Keyless signing via Fulcio/Rekor is unchanged.
sync-community-operators needs COMMUNITY_OPERATORS_PAT, which is
not configured. It runs after the GitHub Release, so it can only
turn a published release red. Skip its steps with a warning when
the secret is empty; behavior with the secret set is unchanged.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
🤖 Generated with Claude Code