Skip to content

fix: drop [skip ci] from publish commit - #11

Merged
lakhansamani merged 1 commit into
mainfrom
fix/publish-skip-ci
Aug 6, 2026
Merged

fix: drop [skip ci] from publish commit#11
lakhansamani merged 1 commit into
mainfrom
fix/publish-skip-ci

Conversation

@lakhansamani

Copy link
Copy Markdown
Contributor

Follow-up to #9. The publish workflow ran correctly on the #10 merge — packaged authorizer-2.2.1.tgz, reindexed, committed and pushed fa70def..5553687. But the chart was still 404 on the site.

Cause: the commit message carried [skip ci], and Netlify honours it. The artifacts reached main but no deploy ran, so the site kept serving the previous build:

  • https://helm-charts.authorizer.dev/Chart.yamlversion: 2.2.1 (deployed by the fix: pull helm test image from quay, not docker hub #10 merge)
  • https://helm-charts.authorizer.dev/charts/authorizer-2.2.1.tgz404 (published by the skipped commit)
  • charts/authorizer-2.2.1.tgz present on main, 16425 bytes

[skip ci] was never needed for loop safety: pushes made with GITHUB_TOKEN do not trigger workflow runs, and the if [ -f "charts/authorizer-${version}.tgz" ] guard makes any re-run a no-op.

Merging this also deploys the already-committed 2.2.1 tarball.

Netlify honours [skip ci] and skipped the deploy, so chart 2.2.1
was committed to main but never served — /charts/authorizer-2.2.1.tgz
returned 404 while Chart.yaml on the site already read 2.2.1.

Loop safety does not need it: GITHUB_TOKEN pushes do not trigger
workflows, and the already-published guard makes a re-run a no-op.
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.

1 participant