Release notes generator
Paste commit messages or pull request titles and get customer facing release notes, sorted into new, improved, and fixed, with internal changes left out.
Link this tool
Embed or cite the release notes generator
Copy a Markdown or HTML badge for your docs, blog, or README. Free, no signup.
How to write release notes customers read
Write for customers, not the commit log
Commit messages say what changed in the code. Release notes say what changed for the customer: what they can do now, what works better, what's fixed. The generator rewrites each line that way and leaves out refactors, tests, and dependency updates.
Lead with the biggest change
Most readers see the headline and nothing else. Make it the change that matters most to customers, in one sentence.
Link the help articles
Every new or changed feature should link to the article that explains it. If that article still describes the old behavior, update it in the same release.
FAQ
Do I need conventional commits?
No. Prefixes like feat: and fix: help sort changes, but plain commit messages and pull request titles work too.
Is my commit history stored?
No. The text is processed once to write the notes and isn't stored. Emails and phone numbers are removed first.
How often should a SaaS publish release notes?
For every release customers would notice, or as a weekly or monthly roundup if you ship many small changes.
Release notes are half the job; the help articles a release touches need updating too. usedocs reads each merged pull request and proposes edits to those articles, with the change attached as evidence.
Start a 7 day free trial