GitPulse v0.1.0 shipped last week, and for the first time, the tool that generates editorial release notes got its own. The system now automatically pulls GitHub releases, matches them to their constituent pull requests, and produces clean, human-readable release notes without any manual intervention. Projects using GitPulse no longer need to maintain changelogs by hand — cut a release and the notes write themselves.
For developers adopting GitPulse, the URLs now follow GitHub conventions — pull requests live at /pull/<n>/ and commits at /commit/<sha>/. A test suite with 53 passing tests and schema validation ensures the analyzer fails loudly in CI rather than silently breaking your deployed site. Proper install documentation means new users are up and running in minutes instead of hours.
The infrastructure is in place: release storage with denormalized top stories, an idempotent hash cache to skip redundant AI calls, and auto-generated Open Graph images. Phase B and beyond now have a stable base to build on.
GitHub releases are now displayed as Special Edition cards on the homepage feed — grouped by publish date and positioned above PR features — with dedicated /releases/ list and detail pages including auto-generated Open Graph images and SEO structured data.
gitpulse now ships with a proper install guide, 53 passing tests, and a schema contract that catches malformed stories before they reach production.
GitPulse now processes GitHub releases end-to-end, automatically matching each release to its PRs and generating editorial-quality release notes — no manual work required.