fix(ci): skip existing chart releases so the Helm index actually publishes

[Vervious]

Tracking issue

Related to #16, #17

Why are the changes needed?

Release Charts still fails after #17, and this is the deeper reason the gh-pages index has been frozen at April 2025.

cr releases every chart under charts/, but only the chart you actually bumped has a new version. Everything else is still at the version released on 2025-04-23, so cr upload fails on the first unchanged chart:

Error: error creating GitHub release flyte-core-v0.1.10:
POST https://api.github.com/repos/exa-labs/flyte/releases:
422 Validation Failed [{Resource:Release Field:tag_name Code:already_exists Message:}]

That exits 1 before the cr index --push step, so the gh-pages index is never regenerated. Every run since that first successful publish was guaranteed to fail this way — #17's dead repository URLs were failing earlier in the job and masking it.

The last run shows how close it gets: packaging succeeded for all six charts, and the release was created —

Successfully packaged chart ... .cr-release-packages/flyte-binary-v0.1.11.tgz
$ gh release list
flyte-binary-v0.1.11   Latest   2026-08-05T18:45:12Z

— but https://exa-labs.github.io/flyte/index.yaml still advertises only v0.1.10, so nothing can consume the chart.

What changes were proposed in this pull request?

Two independent one-liners in .github/workflows/github-helm-charts.yaml:

1. skip_existing: true on helm/chart-releaser-action@v1.6.0. The wrapper maps it to cr upload --skip-existing, so unchanged charts are skipped rather than failing the run, and cr index --push (which the wrapper runs unconditionally afterwards) regenerates the index from the GitHub releases — which already include flyte-binary-v0.1.11.

2. token: ${{ secrets.GITHUB_TOKEN }} on azure/setup-helm@v3, fixing an unrelated warning in the same job:

Error while fetching latest Helm release: [@octokit/auth-action] `GITHUB_TOKEN` variable is not set.
Using default version v3.9.0

The action needs the token to resolve latest; without it the Helm version silently pins to a hardcoded fallback.

How was this patch tested?

Not locally testable — Release Charts only runs on push to master, and the failure is in cr's interaction with the GitHub Releases API, which can't be reproduced from a workstation.

Verified instead against helm/chart-releaser-action@v1.6.0 that skip_existing is a real input on the pinned version, that it maps to cr upload --skip-existing, and that the wrapper invokes cr index --push unconditionally after upload (so skipped uploads don't skip indexing). Likewise confirmed token is a supported input on azure/setup-helm@v3.

The verification that matters is the next push to master: the run should go green and v0.1.11 should appear in https://exa-labs.github.io/flyte/index.yaml.

Labels

fixed

Check all the applicable boxes

• I updated the documentation accordingly. (n/a — CI-only change)
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

• fix(ci): correct stale Helm repository URLs in Release Charts workflow #17 — fixed the stale Helm repository URLs that were failing earlier in this same job.
• Make flyte-binary safe to run with multiple replicas #16 — the HA change whose flyte-binary v0.1.11 is packaged and released but still absent from the index.

Link to Devin session: https://app.devin.ai/sessions/137e980b425d43668660198d80b6e21d
Requested by: @Vervious

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring