Skip to content

chore: publish chart 2.2.0 and automate publishing - #9

Merged
lakhansamani merged 1 commit into
mainfrom
chore/publish-chart-2.2.0
Aug 6, 2026
Merged

chore: publish chart 2.2.0 and automate publishing#9
lakhansamani merged 1 commit into
mainfrom
chore/publish-chart-2.2.0

Conversation

@lakhansamani

Copy link
Copy Markdown
Contributor

Fixes #8helm repo add authorizer https://helm-charts.authorizer.dev tops out at 2.0.1.

Root cause

The repo is served by Netlify straight from the main root (curl https://helm-charts.authorizer.dev/Chart.yaml returns 200 and reads 2.2.0). charts/*.tgz and index.yaml are committed build outputs — nothing ran make build after 2.0.1.

Check Before
Chart.yaml on main 2.2.0 (app 2.3.0)
newest charts/*.tgz authorizer-2.0.1.tgz
index.yaml newest entry 2.0.1, generated: 2026-03-31
/charts/authorizer-2.2.0.tgz 404
workflows test.yml only — no publish job
tags / releases none

README claims a tag push triggers a publishing workflow and that release.sh syncs appVersion. Neither exists.

Changes

  • charts/authorizer-2.2.0.tgz + regenerated index.yaml (make build)
  • .github/workflows/publish.yml — packages, reindexes and commits when Chart.yaml, values.yaml or templates/ change on main

Index diff is the new 2.2.0 entry; the remaining churn is created: timestamps, which helm repo index rewrites without --merge. No existing digest changed.

Verification

  • helm lint clean
  • served over a local HTTP repo: helm repo addrepo updatehelm search repo -l lists 2.2.0/app 2.3.0 → helm pull --version 2.2.0helm template renders image: quay.io/authorizer/authorizer:2.3.0
  • workflow script exercised in four states: version already published (no-op), tgz missing (packages), re-run (no-op, no push loop), version bumped to 2.3.0 (packages and indexes both)
  • main is unprotected and repo Actions default permissions are write, so the workflow can push. GITHUB_TOKEN pushes do not re-trigger workflows.

Merge this before #7. #7 bumps the chart to 2.3.0 but touches neither charts/ nor index.yaml, so on its own it would add a second unpublished version. With this workflow in place, merging #7 publishes 2.3.0 automatically.

helm-charts.authorizer.dev serves this branch root verbatim, but
charts/*.tgz and index.yaml are committed build outputs. Nothing
ran `make build` after 2.0.1, so 2.1.x and 2.2.0 were never
fetchable even though Chart.yaml said 2.2.0.

Workflow packages and reindexes whenever Chart.yaml, values.yaml
or templates/ change on main, so the published index can no
longer drift from the source.

Closes #8
@netlify

netlify Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploy Preview for authorizer-helm-chart ready!

Name Link
🔨 Latest commit 76858e8
🔍 Latest deploy log https://app.netlify.com/projects/authorizer-helm-chart/deploys/6a749b3e036c680008242f09
😎 Deploy Preview https://deploy-preview-9--authorizer-helm-chart.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@lakhansamani
lakhansamani merged commit 39d9bc0 into main Aug 6, 2026
4 checks passed
@lakhansamani
lakhansamani deleted the chore/publish-chart-2.2.0 branch August 6, 2026 14:34
lakhansamani added a commit that referenced this pull request Aug 6, 2026
README documented a tag-triggered workflow and a release.sh that
never existed. Publishing is the workflow added in #9.
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.

Helm chart repo up to date?

1 participant