Skip to content

fix(ci): regenerate helm/README.md and auto-regen on release-please PRs#62

Merged
SoulKyu merged 1 commit intomainfrom
fix/helm-docs-regen-after-release-please
May 6, 2026
Merged

fix(ci): regenerate helm/README.md and auto-regen on release-please PRs#62
SoulKyu merged 1 commit intomainfrom
fix/helm-docs-regen-after-release-please

Conversation

@SoulKyu
Copy link
Copy Markdown
Member

@SoulKyu SoulKyu commented May 6, 2026

Why

After merging the release-please PR (#59) for v3.0.0, the helm-docs-check job on main went red. Cause: release-please bumps helm/Chart.yml and helm/values.yml via the type: generic updater (line-level value replacement) but never invokes helm-docs. helm/README.md is the rendered output of values.yml, so it stayed at 2.0.12 while the source files moved to 3.0.0. The CI gate caught the drift.

What

  1. Immediate fix: regenerate helm/README.md to match the bumped values.yml. 4 lines change (Version badge + 3 image-tag rows in the values table).

  2. Future-proof: patch .github/workflows/release-please.yml with a regen-helm-docs follow-up job. It only runs when release-please opened or updated a PR (if: needs.release-please.outputs.pr != ''), checks out the PR branch, runs make helm-docs, and pushes the regenerated README back to the same branch. From the next release onward, the release-please PR is self-consistent at open time.

Test plan

  • Local make helm-docs produces a clean diff (4 lines)
  • Local make helm-docs-check exits 0 after the regen
  • YAML parse on the modified workflow
  • CI on this PR: helm-docs-check, helm-lint, lint, test, govulncheck, mkdocs-strict, pr-title — all green
  • Future verification: next release-please bump (e.g. v3.0.1 patch) produces a self-consistent PR

Two changes:

1. Regenerate helm/README.md after the release-please-driven bump
   (Chart.yml + values.yml from 2.0.12 -> 3.0.0 left the rendered
   README still showing 2.0.12 because helm-docs reads values.yml at
   regen time, and release-please does not invoke helm-docs). Without
   this fix the helm-docs-check CI gate stays red on main and blocks
   the release.yml workflow.

2. Add a follow-up job to .github/workflows/release-please.yml that
   runs after release-please opens its PR. It checks out the PR
   branch, regenerates helm/README.md, and pushes the result back to
   the same branch. The next release-please bump will produce a
   self-consistent PR — chart files and rendered README in sync, no
   manual regen needed.
@SoulKyu SoulKyu merged commit d413caf into main May 6, 2026
8 checks passed
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