Developer tools

Release Notes Generator

Drop in your commit log or a rough list of changes. The generator recognises Conventional Commits and common keywords, groups everything into clear sections, links issue numbers and formats release notes for developers or for customers.

Runs entirely in your browser. Nothing is uploaded to any server.

Why generate release notes

Save time

Turn a messy commit log into readable notes in seconds.

Consistent format

Every release uses the same sections and style.

Tell users what matters

Hide internal noise and lead with new features and breaking changes.

How to create release notes

  1. Paste changesCopy your commit log or change list into the box, one per line.
  2. Set detailsAdd product name, version, date and optional repository URL.
  3. Pick a style and copyChoose developer or user-friendly style and Markdown, HTML or text.

Writing release notes people read

Lead with what users care about: new features and anything that breaks existing behaviour. Group small fixes together and keep each line short and specific, ideally starting with a verb.

Conventional Commits make this automatic. Prefix commits with feat:, fix:, perf:, docs:, refactor: or chore:, add a scope in brackets when useful, and mark breaking changes with !.

feat

New feature -> Added.

fix

Bug fix -> Fixed.

feat! / BREAKING

Breaking change, listed first.

Release notes FAQ

What input formats are supported?

One change per line. Conventional Commits like "feat(auth): add SSO login" are parsed exactly, including scopes and "!" for breaking changes. Plain lines such as "Fixed crash on upload" are grouped by keywords. Leading bullets and commit hashes are removed.

How are breaking changes detected?

A "!" after the type or scope (feat!: ...) or a line starting with "BREAKING CHANGE:" or "BREAKING:".

How do issue links work?

Enter your repository URL, for example https://github.com/org/repo, and every #123 becomes a link to issue 123. GitHub redirects issue links to pull requests automatically.

What is the user-friendly style?

Friendly headings such as New, Improvements and Bug fixes, capitalised sentences, no scopes, and internal or documentation changes hidden by default.

Does it follow Keep a Changelog?

The developer style uses the Keep a Changelog sections: Added, Changed, Deprecated, Removed, Fixed and Security, plus Performance and Documentation.

Try other developer tools

More free tools from My Panda Toolbox.