From 81c84bc56b3dc7c3c240fa236d77890c2b8f8fb0 Mon Sep 17 00:00:00 2001 From: Lakhan Samani Date: Thu, 6 Aug 2026 20:21:41 +0530 Subject: [PATCH] fix: drop [skip ci] from publish commit MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- .github/workflows/publish.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 7d100ee..5f8200a 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -27,5 +27,8 @@ jobs: git config user.name github-actions git config user.email github-actions@github.com git add "charts/authorizer-${version}.tgz" index.yaml - git commit -m "chore: publish chart ${version} [skip ci]" + # No [skip ci]: Netlify honours it and would not deploy the new chart. + # Loop-safe anyway — GITHUB_TOKEN pushes do not trigger workflows, and + # the guard above makes a re-run a no-op. + git commit -m "chore: publish chart ${version}" git push