Helm chart releases automated alongside package flow
The system now automatically bumps and publishes Helm charts alongside standard package releases, eliminating manual version tracking.
Maintaining parallel release pipelines often creates tedious synchronization tasks. The CI pipeline now automatically handles Helm chart versioning and publishing directly within the standard changeset flow. When a new package release is prepared, the system automatically reads the new package version and updates the Helm chart configuration to match, committing the changes directly to the release branch. Once Docker images are successfully published, the pipeline triggers the Helm release to ensure the chart never references unavailable images. This unifies the release process, removing the need to manually track, bump, and tag Helm charts while keeping the infrastructure deployment artifacts perfectly in sync with the application code.
View Original GitHub Description
Wires up automatic Helm chart releases to ride along with the existing changeset-driven package release flow.
Today Chart.yaml is bumped by hand and release-helm.yml fires only when a human pushes a helm-v* tag. With this, the changeset release PR also carries a Chart.yaml bump so main always matches the published version, and release.yml invokes release-helm.yml via workflow_call after Docker images are published.
helm-v${VERSION} tag is pushed as a marker (same GITHUB_TOKEN trick as v.docker.*). Manual helm-v* tag flow still works. Chart.yaml consistency check in release-helm.yml is the safety net if the bump job ever drifts.
First rollout: the open changeset-release/main PR has stale Chart.yaml. Bump it manually on that branch before merging, otherwise the first automated helm release fails at the consistency check.