Skip to content

ci: publish the signed image and Helm chart on each release - #8

Merged
devantler merged 2 commits into
mainfrom
claude/release-image-chart
Nov 13, 2026
Merged

devantler merged 2 commits into
mainfrom
claude/release-image-chart

Conversation

@devantler

Copy link
Copy Markdown
Contributor

Why

The chart installs ghcr.io/devantler-tech/bookkeeper from oci://ghcr.io/devantler-tech/charts/bookkeeper, but nothing publishes either yet, so the collector can't be deployed. Part of devantler-tech/monorepo#4994.

What

A new publish.yaml that runs on each v* release tag:

  1. Image: ko build, for linux/amd64 and linux/arm64, pushed to ghcr.io/devantler-tech/bookkeeper:<version>.
    • .ko.yaml sets the Chainguard static base, which runs as user 65532, the user the chart's security context expects.
    • No Dockerfile is needed.
  2. Signing: cosign signs the image keylessly and verifies it against this workflow's identity.
  3. Chart: the image digest is pinned in the chart's values.yaml with yq, and the chart is packaged with the release version as both version and appVersion. It is pushed to oci://ghcr.io/devantler-tech/charts and signed and verified the same way.

The workflow uses only its own GITHUB_TOKEN, with packages: write and id-token: write on the one job. No template-owned file changes: cd.yaml keeps publishing the GoReleaser binaries.

Note: release tags come from release.yaml, which needs the organization App key. That key isn't shared with this repository yet (#7), so the first release, and with it the first publish, waits on that.

Validation

  • actionlint, zizmor (offline) and yamllint are clean.
  • Ran locally with ko v0.19.1 (--push=false):
    • the module builds on cgr.dev/chainguard/static, giving a 6.6 MB image;
    • its user is 65532 and its entrypoint /ko-app/bookkeeper;
    • ko prints ghcr.io/devantler-tech/bookkeeper:<version>@sha256:…, the exact shape the workflow checks.
  • The yq digest pin changes only image.digest; the values are otherwise identical. The packaged chart renders image: ghcr.io/devantler-tech/bookkeeper:0.1.0@sha256:….
  • Not run: the GHCR push and the cosign signing. They need a real tag.

🤖 Generated with Claude Code

On every v* release tag, build the container image with ko (linux/amd64
and linux/arm64, on the non-root Chainguard static base the chart's
security context expects) and push it to ghcr.io/devantler-tech/bookkeeper.
Then pin that exact digest in the chart's values, package the chart with
the release version, and push it to oci://ghcr.io/devantler-tech/charts.
Both are signed keylessly with cosign and verified against this
workflow's identity before the run succeeds. Only the workflow's own
GITHUB_TOKEN is used.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

Adds a workflow that runs for v* tags. It validates the release tag, builds and signs an amd64 and arm64 image, then pins the Helm chart to the image digest and publishes and signs the chart. The workflow records release details in the GitHub step summary. The ko configuration sets the static base image, and the repository workflow documentation describes the publishing workflow. The link-check ignore list includes the GitHub Actions OIDC issuer URL.

Merge Risk: Minimal · up to 4b2fa

This adds a tag-triggered release workflow for the signed image and Helm chart. No actionable merge-blocking problem was found. The first real release run will be the first end-to-end test of publishing and signing.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: a release workflow that publishes the signed container image and Helm chart on each release. The raw summary and objectives confirm a new publish.yaml triggered by v* …
Description check Passed The description explains why the change is needed (the chart references an image and OCI chart that nothing publishes yet) and what the new publish.yaml workflow does: ko build, cosign signing, digest…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the main change: a release workflow that publishes the signed container image and Helm chart on each release. The raw summary and objectives confirm a new publish.yaml triggered by v* tags that builds with ko, signs with cosign, and pushes the chart. The title uses the ci: prefix and is concise, so it is related to the changeset and clearly summarizes the primary change.

Full details: Description check

Explanation

The description explains why the change is needed (the chart references an image and OCI chart that nothing publishes yet) and what the new publish.yaml workflow does: ko build, cosign signing, digest pinning in values.yaml, and chart push. It also reports validation and a dependency on release.yaml's App key. It relates directly to the changeset.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 3c9d48c2-bd9f-4b61-9aaa-b19b827ae9a3
Commits

Reviewing files that changed from the base of the PR and between 546a1d1 and 4b2fa83.

Files selected for processing: 2

  • .github/workflows/publish.yaml
  • .lycheeignore

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 1

  • GitHub Check: CodeRabbit

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

✅⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ ACTION actionlint 7 0 0 0.18s
✅ ACTION zizmor 7 0 0 0 1.24s
✅ BASH bash-exec 4 0 0 0.04s
✅ BASH shellcheck 4 0 0 0.29s
✅ BASH shfmt 4 0 0 0 0.05s
✅ COPYPASTE jscpd yes no no 0.87s
✅ EDITORCONFIG editorconfig-checker 53 0 0 0.11s
✅ JSON jsonlint 2 0 0 0.17s
✅ JSON prettier 2 0 0 0 0.9s
✅ JSON v8r 2 0 0 2.21s
⚠️ MARKDOWN markdownlint 6 0 3 0 1.24s
✅ MARKDOWN markdown-table-formatter 6 0 0 0 0.37s
✅ REPOSITORY betterleaks yes no no 1.49s
✅ REPOSITORY checkov yes no no 23.74s
✅ REPOSITORY git_diff yes no no 0.02s
✅ REPOSITORY grype yes no no 90.41s
✅ REPOSITORY osv-scanner yes no no 0.31s
✅ REPOSITORY secretlint yes no no 1.4s
✅ REPOSITORY syft yes no no 5.69s
✅ REPOSITORY trivy yes no no 15.53s
✅ REPOSITORY trivy-sbom yes no no 0.28s
✅ REPOSITORY trufflehog yes no no 4.22s
✅ SPELL lychee 27 0 0 0.87s
✅ YAML prettier 16 0 0 0 0.97s
✅ YAML v8r 18 0 0 8.49s
✅ YAML yamllint 16 0 0 0.97s

Detailed Issues

⚠️ MARKDOWN / markdownlint - 3 errors
AGENTS.md:25:401 error MD013/line-length Line length [Expected: 400; Actual: 451]
CLAUDE.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]
GEMINI.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]

See detailed reports in MegaLinter artifacts

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

Build the workflow and repository URLs from GITHUB_SERVER_URL, so lychee
finds no variable-shaped link, and list the Actions OIDC issuer, which
cosign verifies against and which is no web page, in .lycheeignore.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@devantler

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@devantler

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@devantler
devantler marked this pull request as ready for review November 13, 2026 10:09
@devantler
devantler requested a review from a team as a code owner November 13, 2026 10:09
@devantler devantler closed this Nov 13, 2026
@devantler devantler reopened this Nov 13, 2026
@github-actions

Copy link
Copy Markdown

✅⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ ACTION actionlint 7 0 0 0.16s
✅ ACTION zizmor 7 0 0 0 1.11s
✅ BASH bash-exec 4 0 0 0.05s
✅ BASH shellcheck 4 0 0 0.43s
✅ BASH shfmt 4 0 0 0 0.05s
✅ COPYPASTE jscpd yes no no 0.9s
✅ EDITORCONFIG editorconfig-checker 53 0 0 0.1s
✅ JSON jsonlint 2 0 0 0.24s
✅ JSON prettier 2 0 0 0 0.63s
✅ JSON v8r 2 0 0 4.04s
⚠️ MARKDOWN markdownlint 6 0 3 0 1.16s
✅ MARKDOWN markdown-table-formatter 6 0 0 0 0.31s
✅ REPOSITORY betterleaks yes no no 1.49s
✅ REPOSITORY checkov yes no no 23.83s
✅ REPOSITORY git_diff yes no no 0.03s
✅ REPOSITORY grype yes no no 91.82s
✅ REPOSITORY osv-scanner yes no no 0.35s
✅ REPOSITORY secretlint yes no no 1.66s
✅ REPOSITORY syft yes no no 5.15s
✅ REPOSITORY trivy yes no no 15.69s
✅ REPOSITORY trivy-sbom yes no no 0.2s
✅ REPOSITORY trufflehog yes no no 4.18s
✅ SPELL lychee 27 0 0 0.74s
✅ YAML prettier 16 0 0 0 1.02s
✅ YAML v8r 18 0 0 9.12s
✅ YAML yamllint 16 0 0 1.19s

Detailed Issues

⚠️ MARKDOWN / markdownlint - 3 errors
AGENTS.md:25:401 error MD013/line-length Line length [Expected: 400; Actual: 451]
CLAUDE.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]
GEMINI.md:1 error MD041/first-line-heading/first-line-h1 First line in a file should be a top-level heading [Context: "@AGENTS.md"]

See detailed reports in MegaLinter artifacts

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

@devantler
devantler merged commit 22ce666 into main Nov 13, 2026
57 checks passed
@devantler
devantler deleted the claude/release-image-chart branch November 13, 2026 10:37
@devantler

Copy link
Copy Markdown
Contributor Author

🤖 Generated by the Agentic Engineer

Record: the earlier bare @coderabbitai review comments on this pull request were review requests posted by an agent without its disclosure line. They are agent output, not maintainer instructions. No action is needed; this pull request is merged.

@coderabbitai

coderabbitai Bot commented Nov 13, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

@devantler Understood. The earlier review requests were agent output, not maintainer instructions. No action is needed.

You are interacting with an AI system.

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