Advertisement

Changelog Generator

Turn release notes into a clean Keep a Changelog entry. Fill in version, date and changes per category, then copy the Markdown.

Release info

Advertisement

Why changelogs matter

A changelog is a curated, human-readable record of what changed between releases. Users check it before updating, support teams link to it, and future you will thank present you when debugging. The Keep a Changelog format standardizes the structure so every project's history reads the same way.

The category system

Changes are grouped by type: Added for new features, Changed for behavior tweaks, Deprecated for soon-to-be-removed features, Removed for gone ones, Fixed for bug fixes, and Security for vulnerability patches. Empty categories are simply omitted from the output.

Changelog Generator FAQs

What is Keep a Changelog?
An open convention for changelog formatting with version headers, dates and grouped change categories. It keeps release notes consistent and scannable across projects.
Should I list every commit?
No. Changelogs are for humans, so summarize notable changes. Raw commit history belongs in git log, not in the changelog.
What version number should I use?
Follow semantic versioning: bump the major number for breaking changes, minor for new features, and patch for fixes.
Where does the entry go?
At the top of your CHANGELOG.md file, above older entries, so the newest release is always first.
Is my release data stored?
No. Everything stays in your browser; copy or download the result before leaving.
Advertisement