Skip to content

Conversation

@aRustyDev
Copy link
Owner

Summary

Fixes Cosign deprecation warning by signing OCI artifacts by digest instead of tag.

Problem

Cosign warns when signing by tag (e.g., chart:0.2.1):

WARNING: Image reference ghcr.io/arustydev/charts/mdbook-htmx:0.2.1 uses a tag, not a digest...

Signing by tag is a security concern because the tag could point to a different image between push and sign operations.

Solution

  • Capture digest from helm push output (format: Digest: sha256:...)
  • Sign using chart@sha256:abc123... instead of chart:version
  • Combined push and sign into single step for atomic operation

Changes

  • publish-ghcr.yaml - Combined publish + sign, uses digest
  • release-please.yaml - Combined push + sign, uses digest

Test plan

  • Run: gh workflow run publish-ghcr.yaml -f charts=all -f sign=true
  • Verify no Cosign deprecation warning
  • Verify signing uses digest format in logs

🤖 Generated with Claude Code

### Changed
- Capture digest from `helm push` output
- Sign using `$REGISTRY/chart@sha256:...` instead of `$REGISTRY/chart:version`
- Combined push and sign into single step for atomic operation

This fixes Cosign deprecation warning about signing by tag and ensures
we sign exactly the image we just pushed (more secure).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cloudflare-workers-and-pages
Copy link

Deploying helm-charts with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4d6a8b8
Status: ✅  Deploy successful!
Preview URL: https://7c5dac8a.helm-charts-76l.pages.dev
Branch Preview URL: https://fix-cosign-sign-by-digest.helm-charts-76l.pages.dev

View logs

@aRustyDev aRustyDev merged commit abef252 into main Jan 6, 2026
12 checks passed
@aRustyDev aRustyDev deleted the fix/cosign-sign-by-digest branch January 6, 2026 08:47
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.

2 participants