fix(ci): authenticate cosign + lowercase image ref so v0.2.0 signs - #41
Merged
Conversation
The first v0.2.0 release pushed every artifact but failed both cosign
signing steps:
- chart.yml: cosign reads ~/.docker/config.json, but the job only ran
`helm registry login` (Helm's own credential store), so the signature
push got UNAUTHORIZED. Add docker/login-action alongside the Helm login
to populate both stores.
- release.yml: the cosign step signed `ghcr.io/${{ github.repository }}`,
which is mixed-case (AYDEV-FR/dploy); OCI refs must be lowercase, so
cosign failed with "could not parse reference". Lowercase the ref and
sign the build's immutable digest instead of the mutable tag.
Both fixes only affect signing — the chart and images themselves were
already published successfully.
Claude-Session: https://claude.ai/code/session_01M4Dd5oASBGHwr6ts6wTnYn
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.
Context
The first
v0.2.0tag triggered the release pipeline. Every artifact published successfully (GitHub Release, binaries,api/operatorimages, and the OCI chart), but both cosign signing steps failed:chart.ymlUNAUTHORIZEDwhen cosign pushed the chart signaturerelease.ymlcould not parse reference: ghcr.io/AYDEV-FR/dploy:0.2.0Root causes & fixes
chart.yml— cosign had no credentials. cosign reads~/.docker/config.json, but the job only ranhelm registry login, which writes to Helm's own credential store. Sohelm pushworked, but the signature push was unauthenticated. Fix: adddocker/login-actionalongside the Helm login so both stores are populated.release.yml— uppercase OCI reference. The cosign step signedghcr.io/${{ github.repository }}=ghcr.io/AYDEV-FR/dploy. OCI references must be lowercase, so cosign rejected it. Fix: lowercase the reference and sign the build's immutable@sha256:…digest instead of the mutable tag.Both changes touch only the signing steps — the artifacts themselves were already published.
Not addressed here
release.yml's "Deploy to GitHub Pages" step also failed (ENOENT docs/build). That's a pre-existing, unrelated docs-deploy issue — left out of this PR to keep it scoped.Re-running v0.2.0
Once merged, the
v0.2.0tag will be re-pointed at the new HEAD to re-run the pipeline; signing is idempotent against the already-pushed artifacts.https://claude.ai/code/session_01M4Dd5oASBGHwr6ts6wTnYn