helm-update

Helm Update

Apply changes to the Bifrost Helm chart, keep it in sync with config.schema.json, and update all changelogs.

Key File Paths

File	Path
Config schema	transports/config.schema.json
Chart metadata	helm-charts/bifrost/Chart.yaml
Values	helm-charts/bifrost/values.yaml
Values schema	helm-charts/bifrost/values.schema.json
Helpers template	helm-charts/bifrost/templates/_helpers.tpl
Helm README	helm-charts/bifrost/README.md
Docs changelogs	docs/changelogs/helm-v<version>.mdx
Docs navigation	docs/docs.json

---

Workflow

Step 1: Gather Current State

Read the current helm chart version and identify the last helm release commit:

# Current helm chart version
cat helm-charts/bifrost/Chart.yaml | grep '^version:'

# Latest docs helm changelog (= last released version)
ls -1t docs/changelogs/helm-v*.mdx | head -1

# Find the commit that added the latest helm changelog
LAST_HELM_MDX=$(ls -1t docs/changelogs/helm-v*.mdx | head -1)
git log --oneline -- "$LAST_HELM_MDX" | head -1

Save the last-release commit SHA — you'll need it to scope the config.schema.json diff.

Step 2: Check config.schema.json Changes Since Last Helm Release

LAST_COMMIT=$(git log --oneline -- "$(ls -1t docs/changelogs/helm-v*.mdx | head -1)" | awk '{print $1}')

# What changed in config.schema.json since then?
git diff ${LAST_COMMIT}..HEAD -- transports/config.schema.json

Identify any fields added, removed, or changed in config.schema.json that are not yet reflected in the helm chart. These are gaps that must be closed — even if the user did not explicitly ask for them. Note each gap; you will apply them alongside the user's requested changes.

Step 3: Apply User-Requested Changes + Fill Gaps

For every change (user-requested AND schema gaps detected in Step 2):

values.yaml

Add new fields as commented-out blocks with a realistic sample value. Place new sections near related existing fields. Keep existing uncommented defaults intact.