Set up a `gh-pages` branch in your repository to serve as the Helm chart repository index
Add the `helm/chart-releaser-action` GitHub Actions workflow to your repo; configure it with `charts_dir` pointing to your charts directory and a GitHub token secret
On each push to the default branch, the action packages changed charts, uploads them as GitHub release assets, and updates the `index.yaml` on `gh-pages`
Consumers add your chart repo with `helm repo add <name> https://<your-org>.github.io/<repo>` and install with `helm install <release> <name>/<chart>`
Bump `version` in `Chart.yaml` for each release; chart-releaser detects version changes to know which charts have changed and need releasing
For multi-chart monorepos, chart-releaser handles each chart independently — each gets its own GitHub release tagged `<chart-name>-<version>`
Known gotchas
chart-releaser only releases charts whose `version` field in Chart.yaml has changed since the last tagged release — forgetting to bump the version means no release is created, even if chart content changed
The `gh-pages` index is updated by pushing directly from the action; if branch protection is enabled on `gh-pages`, the action's token needs bypass permission or the push will fail
Helm chart repositories served via GitHub Pages are not OCI registries — if you need OCI push/pull (`helm push`), you need a separate OCI registry (GHCR, ECR, etc.) rather than the chart-releaser pattern
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp