Self-deploy workflow updated to track main
GitHub Actions workflow pin updated to eliminate a deployment blocker affecting gitpulse's own CI pipeline.
Gitpulse's self-deploy workflow was stuck failing. It pinned to publish-pages.yaml@v0, which had floated to v0.1.4 — a version containing a broken npx command. The fix was on main, but workflow file changes don't bump the CLI package version, so v0 stayed frozen with no path forward.
The self-deploy workflow now tracks @main instead of @v0. This immediately picks up the working version on next push, keeping the pipeline evergreen. The tradeoff is accepted because self-deploy is gitpulse's own infrastructure — the team controls main directly. External consumers continue pinning to @v0 or @v1 for stability and are unaffected.
In the deployment pipeline, this unblocks the only remaining red workflow.