Gitpulse
The Gitpulse Dispatch
Friday, May 22, 2026

The Gitpulse Dispatch

Development activity intelligence for gitpulse itself

Thursday, May 7, 2026

Release Edition
v0.1.5

“Own dogfood, own CI, now with dotfiles.”

Release — v0.1.5
Editorial illustration for release v0.1.5
4
PRs Merged
2
Contributors
+152
Lines
Top Stories
  • 1Custom publication titles supported via .gitpulse.jsonDevelopers can now set custom publication titles and move per-project settings into a committed .gitpulse.json file instead of managing them through environment variables.Feature
  • 2GitHub Actions CI unblocked with global CLI installDeployments can now run reliably on GitHub Actions. The fix swaps a broken npx invocation for a global npm install that works on Linux runners.Fix
  • 3Gitpulse CLI bumped to version 0.1.5Version 0.1.5 of the Gitpulse CLI has been released, including support for a .gitpulse.json config file that lets users set custom publication titles and subtitles.
Read the Full Edition→4 stories inside
New Feature·Merged May 7, 2026·M

Custom publication titles supported via .gitpulse.json

#41·by @znat

Developers can now set custom publication titles and move per-project settings into a committed .gitpulse.json file instead of managing them through environment variables.

Monday, May 4, 2026

Release Edition
v0.1.4

“The CLI now asks your hosting provider where it lives. We didn't teach it manners.”

Release — v0.1.4
Editorial illustration for release v0.1.4
4
PRs Merged
2
Contributors
+475
Lines
Top Stories
  • 1Site URL auto-detected from Vercel, Netlify, Cloudflare PagesDeploying gitpulse no longer requires setting GITPULSE_SITE_URL manually — the CLI now detects your site URL automatically from Vercel, Netlify, and Cloudflare Pages environment variables at build time.Feature
  • 2Deployment workflows fixed with correct npx syntaxGitHub Actions workflows and documentation examples now use the correct explicit npx invocation, fixing deployments that were silently failing with "command not found" errors.Fix
  • 3GitPulse CLI 0.1.4 releasedVersion 0.1.4 of GitPulse CLI is now available, capturing internal tooling improvements including dogfooded CLI usage, Vercel deployment config, and an updated README.
Read the Full Edition→4 stories inside
Release Edition
v0.1.2

“"We fixed the package.json math. One package gets published, not two."”

Release — v0.1.2
Editorial illustration for release v0.1.2
2
PRs Merged
2
Contributors
+75
Lines
Top Stories
  • 1Release automation unblocked after tag collision fixRelease-please was managing two packages and colliding on git tags whenever versions diverged — five PRs failed to publish. The root package is private, never published to npm, and shouldn't have been in the release pipeline at all.
  • 2GitPulse 0.1.2 unblocks release pipelineGitPulse 0.1.2 drops a problematic plugin and fixes documentation alignment to get the automated release workflow moving again.
Read the Full Edition→2 stories inside
Release Edition
v0.1.3

“We taught an LLM to read git diffs and write better than half of us.”

Release — v0.1.3
Editorial illustration for release v0.1.3
3
PRs Merged
2
Contributors
+110
Lines
Top Stories
  • 1GitPulse v0.1.3 released with LLM story pipelineVersion 0.1.3 brings a complete local git → LLM → story pipeline, full editorial site redesign, new CLI package, and 12 bug fixes including reasoning block handling and SEO improvements.
  • 2Release plugin removed, pipeline unblockedMonorepo releases should flow freely again after removing a plugin that was blocking version bumps when only one package had changes.Fix
  • 3gitpulse v0.1.2 released with release-please fixVersion 0.1.2 is out, bundling a fix for Release Please so it works correctly in monorepos where linked-versions isn't available.
Read the Full Edition→3 stories inside
Release Edition
v0.1.1

“The CLI shipped. Your analytics now deploy themselves.”

Release — v0.1.1
Editorial illustration for release v0.1.1
7
PRs Merged
2
Contributors
+4.8k
Lines
Top Stories
  • 1PR detail page redesigned with tabs and diff viewerThe gitpulse PR detail page now shows richer metadata up front—merged status, size assessment, and category breakdown—before the headline. Story and technical content live in separate tabs, with code blocks rendering line numbers and diffs getting green/red coloring.Feature
  • 2PR details open in slide-in drawer with scroll preservedClicking any feed item now slides PR or commit details in from the right instead of navigating away. The feed stays frozen at its scroll position, and closing the drawer returns users exactly where they were. The panel is deep-linkable via URL.Feature
  • 3Gitpulse CLI shipped to npm with reusable Pages workflowA new CLI package lets any project publish its gitpulse analytics to GitHub Pages, Vercel, Netlify, or custom infrastructure — no bundler or token management required.Feature
Read the Full Edition→7 stories inside
New Feature·Merged May 4, 2026·M

Site URL auto-detected from Vercel, Netlify, Cloudflare Pages

#35·by @znat

Deploying gitpulse no longer requires setting GITPULSE_SITE_URL manually — the CLI now detects your site URL automatically from Vercel, Netlify, and Cloudflare Pages environment variables at build time.

Fixes & Patches