Release Edition
v0.1.5

Config moved to JSON. CI moved to global. Gitpulse now respects Linux and preferences.

v0.1.5 · May 7, 2026

Gitpulse publications can now have custom titles and subtitles without touching source code. Maintainers drop a .gitpulse.json file at the repo root to set publication preferences, adjust how analysis runs, and tune dispatch titles — all in one place. Your newsletter header just became your problem, not the CI's.

CI deployments work reliably on Linux now. The gitpulse CLI installs globally instead of relying on npx, which was hitting a PATH resolution bug on Linux runners while macOS sailed through unaffected. If your pipeline runs on multiple operating systems, you can finally trust it.

The self-deploy workflow has been un-stuck. It now tracks @main for the publish-pages action instead of a broken pinned version, meaning gitpulse's own CI should go green and fixes can ship immediately without waiting for a formal release. The projectdog is eating its own dog food, and the bowl is clean.

← All Releases
4
PRs Merged
2
Contributors
+122
Additions
-30
Deletions
Top Stories
1
feature

Custom publication titles arrive in Gitpulse

#41·by @znat·+98 / -16

Gitpulse now reads a .gitpulse.json file at the repo root, letting maintainers set custom publication titles and subtitles alongside per-project analysis preferences.

2
bugfix

CI deployment pipelines fixed on Linux runners

#39·by @znat·+14 / -11

GitHub Actions deployment workflows now work reliably — the gitpulse CLI installs globally instead of relying on npx, which was hitting a PATH resolution bug on Linux runners.

  • 4
    Self-deploy workflow points to @main
    The self-deploy workflow was stuck on a broken pinned version of the publish-pages action, failing every run. It's now tracking @main for immediate fixes.
    bugfix