GitPulse deployments now run entirely through GitHub Actions, with secrets staying in the runner and Vercel handling only hosting duties. Site URLs are also now detected automatically when running on Vercel, Netlify, or Cloudflare Pages — no GITPULSE_SITE_URL configuration required on those platforms.
Documentation and CI workflows have been corrected to use explicit npx syntax, resolving an issue that silently broke automated deployments and could have misled anyone reading the setup guide.
The CLI package has reached version 0.1.4 and is now publishing its own releases, completing the dogfooding loop. Release automation has also been cleaned up after a versioning issue in the prior release.
GitPulse now deploys to Vercel using a CI-first pattern where GitHub Actions runs the analytics build and Vercel just hosts the output — keeping all secrets in the runner. Site URLs are also now auto-detected from platform environment variables on Vercel, Netlify, and Cloudflare Pages, eliminating manual GITPULSE_SITE_URL configuration.
GitHub Actions deployments were silently failing because the CLI binary name didn't match npx's shorthand resolution. A quick syntax update to explicit `--package=` form puts deployments back on track—and prevents anyone reading the docs from hitting the same wall.
Version 0.1.4 of the GitPulse CLI is now released, marking the project's own CLI tool as production-ready while fixing release automation issues that caused a version reset in the prior release.