Pushpen turns your commit history into meaningful, categorized release notes. Every time you tag a release, it generates notes your users can actually read — no more dumping raw git logs into GitHub Releases.
Release notes are your users' primary source of truth for what changed. But writing them well takes time, and writing them poorly wastes your users' time. Pushpen bridges the gap: it reads your commit history, understands the intent behind each change, and produces categorized release notes that explain what changed, why, and what users need to know.
Start freeThe problem
Pasting git log output into a release is fast but useless. “Fix null pointer in auth middleware” tells users nothing about whether they need to update or what changed behaviorally.
Writing proper release notes takes 30 minutes per release. Teams shipping weekly spend a full day each month writing notes that most users will skim once and forget.
How it works
Pushpen monitors your repository for new version tags and generates release notes scoped to each release.
Tag a release normally — git tag v1.2.3 && git push --tags. Pushpen detects the new tag automatically.
Pushpen reads all commits since the previous tag, categorizes them, and translates implementation details into user-facing descriptions.
AI produces categorized release notes grouped by type: Added, Fixed, Changed, Deprecated, Removed, Security.
Pushpen opens a PR with release notes for review, or publishes directly to GitHub Releases — your choice.
Features
Detects versions from git tags and version files. Generates notes scoped to each release, never mixing changes across versions.
Groups commits into Added, Fixed, Changed, Deprecated, Removed, and Security. Works with or without conventional commits.
Publishes directly to GitHub Releases or opens a PR for review. Integrates with your existing release workflow.
FAQ
Pushpen analyzes your commit history, groups related commits, categorizes changes into Added, Fixed, Changed, and Removed, and translates implementation details into user-facing descriptions. It follows Keep a Changelog conventions by default.
Yes. Pushpen can automatically create GitHub Release entries with generated release notes when you tag a release. It maps git tags to versions and generates notes scoped to each release.
Yes. Pushpen generates PRs with release notes that you can review and edit before publishing. You can customize the categorization rules, the level of detail, and the output format to match your team's conventions.
Pushpen reads git tags and version files (package.json, Cargo.toml, version.rb, etc.) to detect new releases. When a new version tag is pushed, it generates release notes containing only commits since the previous tag.
Pushpen uses AI to categorize commits regardless of format. While conventional commits improve accuracy, the AI model can understand the intent of any commit message and classify it appropriately.