RELEASE NOTES GENERATOR · RUNS IN YOUR BROWSER

Turn your git log into release notes

Paste commits, get a CHANGELOG.md entry or GitHub release notes: grouped by Conventional Commit type, breaking changes first, pull requests linked, and a suggested semantic version bump. Older histories without conventions still work: the section is guessed from the first word and flagged.

Nothing is uploaded. Your commit text stays in this tab and the page makes no network calls.

Your commits

Get them with: git log --format='%H%x1f%an%x1f%s%x1f%b%x1e' v1.2.0..HEAD (or just run the CLI below). Plain git log --oneline output also works.

Paste commits and click Generate.

Run it on your repo from the command line

node cli.mjs --from v1.2.0 --version 1.3.0 --repo https://github.com/owner/repo
node cli.mjs --from v1.2.0 --bump          # prints: minor -> v1.3.0
node cli.mjs --style github --authors --skip chore,ci,test

Get cli.mjs and changelog.mjs from the repo. Node 18+, git, no dependencies.

Common questions

How do I generate release notes from git commits?

Run git log between two tags with the format this tool documents, or just run the CLI, which calls git for you. Commits are grouped by Conventional Commit type (feat, fix, perf and so on), breaking changes are pulled to the top, and non-conventional subjects are classified by their first word so an older history still produces something usable.

How does it decide the next version number?

By Semantic Versioning: any breaking change suggests a major bump, otherwise any feat suggests minor, otherwise patch. Before 1.0.0 a breaking change suggests minor. It is a suggestion from commit messages only; you decide the release.

Does this upload my commit history?

No. Everything runs in this page. The page makes no network calls and your commit text is never uploaded. The CLI runs git on your machine and prints to your terminal.

What output formats are supported?

Keep a Changelog style Markdown for CHANGELOG.md, GitHub release style notes with a What's changed heading, and plain text for emails and store listings. Pass a repository URL to link pull requests and commits.

Is this a replacement for release-please or git-cliff?

It overlaps with them on purpose. Use it when you want the notes now, without installing anything or configuring a pipeline, or to preview what your history will produce. It does not publish releases or edit files for you.

More: how to write a changelog people read (and automate the boring half)