From bb34d80869353fb8faacb72cb10645adff318178 Mon Sep 17 00:00:00 2001 From: Nathan Zylbersztejn Date: Mon, 4 May 2026 23:31:43 +0200 Subject: [PATCH] fix(self-deploy): track publish-pages.yaml@main instead of @v0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit self-deploy was stuck failing because it pinned publish-pages.yaml@v0 (currently floating to v0.1.4) which still has the broken npx form. Workflow/README fixes don't bump the cli package, so v0 won't advance on its own without a cli-touching commit. Since self-deploy is gitpulse's own dogfood (not the external consumer surface), tracking @main is fine — we get the fix immediately and stay on bleeding-edge by definition. External consumers continue pinning @v0 / @v1 for stability; their experience is unaffected. Could revert to @v0 after a cli-touching change ships and floats v0 forward, but there's no strong reason to. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/self-deploy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/self-deploy.yml b/.github/workflows/self-deploy.yml index 1f5a53d..cc44fb1 100644 --- a/.github/workflows/self-deploy.yml +++ b/.github/workflows/self-deploy.yml @@ -26,7 +26,7 @@ permissions: jobs: publish: - uses: znat/gitpulse/.github/workflows/publish-pages.yaml@v0 + uses: znat/gitpulse/.github/workflows/publish-pages.yaml@main with: ai-protocol: openai ai-base-url: https://api.minimax.io/v1