Open source changelogs carry extra weight
For a library or tool, the changelog isn't a nicety — it's part of the public contract. People depend on your code, and they read the changelog to decide whether an upgrade is safe. That puts unusual demands on it: breaking changes must be unmissable, migration paths need to be spelled out, and the format should be one contributors already recognise so PRs can update it consistently.
This generator leans into that — it defaults to Keep a Changelog, surfaces anything that looks breaking, and keeps entries terse enough to scan across dozens of versions.
Breaking changes get top billing
Made for the contributor workflow
- Recognisable format — Keep a Changelog, so contributors know exactly where to add their line.
- An
[Unreleased]section to collect changes between releases. - Semver-aware — breaking changes signal a major bump.
- No account or repo link — paste the log; nothing is sent to a third party but the text.
FAQ
Does it follow Keep a Changelog?
Yes, by default — see the dedicated Keep a Changelog generator for the format details.
How does it spot breaking changes?
It flags removals, signature changes, and anything your commits mark as breaking (e.g. feat!: or "BREAKING CHANGE"). Always review these before publishing.
Is it free for open source?
You get one free generation without an account; ongoing use is the Solo plan at freenth.
Try it on your commits
Paste your commits, pick a format, copy the result. Unlimited free generations, no account.
try free →