fix(self-deploy): track publish-pages.yaml@main (immediate fix unblock)

[znat]

self-deploy is the only red workflow left; deploy-vercel just went green on 8a27e8d with the npm install -g fix.

self-deploy fails because it pins publish-pages.yaml@v0 and v0 floats to v0.1.4 — which has the broken npx form. The fix on main only affects publish-pages.yaml's content, but workflow files don't bump the cli package, so release-please won't propose a 0.1.5 release that would float v0 forward.

This PR: self-deploy → publish-pages.yaml@main. Picks up the fix immediately on next push, stays evergreen.

Trade-off: self-deploy is no longer pinned. Acceptable because:

• It's gitpulse's own dogfood (we control main)
• External consumers still pin @v0 / @v1 for stability
• Bleeding-edge is what we want for our own deploy

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated deployment workflow configuration to reference the latest version from the main branch instead of a pinned release version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9208d6fc-d1a4-432b-8e60-0f81412cc1d5

📥 Commits

Reviewing files that changed from the base of the PR and between 8a27e8d and bb34d80.

📒 Files selected for processing (1)

• .github/workflows/self-deploy.yml

---

📝 Walkthrough

Walkthrough

The publish job in .github/workflows/self-deploy.yml now references the reusable publish-pages.yaml workflow from the main branch instead of the pinned v0 tag, updating which workflow definition executes during self-deploy events.

Changes

Workflow Configuration Update

Layer / File(s)	Summary
Reusable Workflow Reference .github/workflows/self-deploy.yml	jobs.publish.uses is updated to reference znat/gitpulse/.github/workflows/publish-pages.yaml@main instead of @v0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• znat/gitpulse#37: Main PR changes the self-deploy workflow to reference the reusable publish-pages.yaml at @main instead of the pinned @v0, which directly affects which version of the publish-pages.yaml (the file modified by the retrieved PR) is used — related.
• znat/gitpulse#35: Both PRs modify the same workflow reference in .github/workflows/self-deploy.yml (the jobs.publish.uses reusable-workflow call), so they are related.

Poem

🐰 A workflow once locked to v0's door,
Now chases the main branch and something more!
No pinned old version, just living edge alive,
Where changes flow fresh—and our deploys thrive! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: updating the self-deploy workflow to track publish-pages.yaml@main instead of @v0, which directly addresses the PR's primary objective of unblocking the broken workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/self-deploy-tracks-main

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR changes the self-deploy workflow's reusable workflow reference from the pinned @v0 tag to @main, picking up the npx fix in publish-pages.yaml without waiting for a v0.1.5 release. The trade-off (mutable @main ref instead of a pinned tag) is explicitly documented and appropriate for an owner-controlled dogfood deployment.

Confidence Score: 5/5

Safe to merge — minimal one-line change with a well-reasoned and documented trade-off.

Single targeted change that unblocks the self-deploy workflow. No logic errors, no security concerns, and the author explicitly documents the stability trade-off. No other files are affected.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/self-deploy.yml	Single-line change unpins the reusable workflow reference from @v0 to @main; intentional trade-off acknowledged in PR description

Sequence Diagram

sequenceDiagram
    participant Push as Push to main
    participant SelfDeploy as self-deploy.yml
    participant PublishPages as publish-pages.yaml@main
    participant CLI as npx @gitpulse/cli@0
    participant Pages as GitHub Pages

    Push->>SelfDeploy: trigger (push/release/dispatch)
    SelfDeploy->>PublishPages: uses (was @v0, now @main)
    PublishPages->>CLI: npm install -g @gitpulse/cli@0
    CLI->>CLI: analyze + build
    CLI->>Pages: deploy artifact

Loading

_{Reviews (1): Last reviewed commit: "fix(self-deploy): track publish-pages.ya..." | Re-trigger Greptile}