Setting up gitpulse no longer requires hunting down your site URL and configuring environment variables. The CLI now detects your deployment address automatically when running on Vercel, Netlify, or Cloudflare Pages — one less step during setup, and one less thing that can go wrong.
Deployments that appeared to succeed were actually silently failing at runtime because the npx invocation couldn't locate the CLI binary. Scripts have been corrected to use the proper invocation syntax, so your analytics now update as intended when the workflow runs.
The team is also dogfooding gitpulse to track gitpulse development — the tool now monitors itself. Future releases will arrive with their own changelog entry, which feels appropriately recursive.
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.
GitHub Actions workflows and documentation examples now use the correct explicit npx invocation, fixing deployments that were silently failing with "command not found" errors.
Version 0.1.4 of GitPulse CLI is now available, capturing internal tooling improvements including dogfooded CLI usage, Vercel deployment config, and an updated README.