Changelog Generator

Paste a Conventional Commits blob — one commit per line, or separated by blank lines, or split by the ==END== sentinel — and get a Keep-a-Changelog Markdown release entry. Breaking changes are surfaced in a top section, the next semver bump is suggested from the rule of thumb (BREAKING → major, feat → minor, else → patch), and the output is ready to paste into CHANGELOG.md. Pure client-side, no upload.

—
Release config — version, date, and the compare-link base
Summary — recomputed live
Suggested next — awaiting input
Conventional 0 0 unparsed
Breaking 0 ⚠ top section
Sections 0 0 entries
Markdown
— 
Paste commits above to see the Markdown.
How the generator works
  • Input shape — one commit per line, separated by blank lines (a paragraph break), or split by the ==END== sentinel line. The page normalises line endings and trims whitespace.
  • Conventional types — feat, fix, refactor, perf, style, revert, docs, test, build, ci, chore. Unknown types fall into the maintenance section.
  • Section buckets — feat → Added, fix → Fixed, refactor/style → Changed, perf → Performance, revert → Removed, the rest → Maintenance.
  • Breaking changes — detected from the ! marker in the header (feat(api)!: drop) AND from the BREAKING CHANGE: footer. Promoted to a top section.
  • Suggested next version — BREAKING wins (major), else feat bumps minor, else patch. Set Current version to enable the math; leave it blank for the very first release (0.1.0).
  • Scope markers — feat(api): … renders as - … (**api**) in the bullet list, so the audience can spot the touched area at a glance.
  • Compare URL — rendered as a [Compare changes](url) link at the bottom of the entry. Pass the git compare URL of the two releases.
  • Everything runs locally. Nothing leaves the browser.