Helm chart repo up to date? #8

Activity

1. lakhansamani

   added 3 commits that reference this issue on Aug 6, 2026

   chore: publish chart 2.2.0 and automate publishing

   ...

   This issue will close once commit d2d2cc7 is merged into the 'main' branch.

   d2d2cc7

   chore: publish chart 2.2.0 and automate publishing

   ...

   This issue will close once commit 76858e8 is merged into the 'main' branch.

   76858e8

   chore: publish chart 2.2.0 and automate publishing

   ...

   This issue will close once commit 39d9bc0 is merged into the 'main' branch.

   39d9bc0
2. lakhansamani

   closed this as completedin #9on Aug 6, 2026
3. lakhansamani commented on Aug 6, 2026

   

   lakhansamani

   on Aug 6, 2026

   Contributor

   More actions

   Thanks for the clear repro — the repo hasn't moved, it was just stale. Fixed now: 2.2.0 is live.

   $ helm repo update && helm search repo authorizer -l | head -3
   NAME                    CHART VERSION   APP VERSION
   authorizer/authorizer   2.2.0           2.3.0
   authorizer/authorizer   2.0.1           2.0.1
   

   https://helm-charts.authorizer.dev/charts/authorizer-2.2.0.tgz now returns 200.

   What was wrong

   helm-charts.authorizer.dev is served straight from the main branch root, and charts/*.tgz + index.yaml are committed build outputs. Chart.yaml on main said 2.2.0, but nobody ran make build after 2.0.1 — so the packaged tarball and the index were never regenerated. The published index was last generated 2026-03-31. There was no CI publishing step either (the README claimed a tag-triggered workflow, which didn't exist), so this was guaranteed to drift again.

   Fix

   #9 publishes 2.2.0 and adds .github/workflows/publish.yml, which packages the chart and regenerates the index whenever Chart.yaml, values.yaml or templates/ change on main. No more manual step.

   Verified end to end on kind

   helm repo add authorizer https://helm-charts.authorizer.dev
   helm install authorizer authorizer/authorizer --version 2.2.0 \
     --namespace authorizer --create-namespace --wait \
     --set authorizer.database_type=sqlite \
     --set authorizer.database_url="/tmp/authorizer.db" \
     --set authorizer.client_id=... --set authorizer.client_secret=... \
     --set authorizer.admin_secret=... \
     --set authorizer.jwt_type=HS256 --set authorizer.jwt_secret=... \
     --set securityContext.readOnlyRootFilesystem=false
   

   • pod Running on quay.io/authorizer/authorizer:2.3.0
   • helm test → Phase: Succeeded
   • /healthz → 200, /.well-known/openid-configuration serves

   Note securityContext.readOnlyRootFilesystem=false is required for sqlite — the root filesystem is read-only by default and there is no volume option yet, so the DB file can't be written otherwise. Postgres needs no such override.

   2.3.0 is queued behind #7 and will publish automatically once that merges. Sorry for the stale window, and thanks for reporting it.