Release Notes Generator

A release notes template that doesn't suck.

Free release notes generator with a clean Markdown template. Add a version and date, drop your changes into Added / Fixed / Changed buckets, and export as Keep a Changelog, a GitHub release, or a Slack post.

Free template3 output formatsWorks with semantic versioning

Project info

Used to link version tags to GitHub releases

Import from git log

Paste output of: git log --oneline. We auto-classify Conventional Commits (feat → Added, fix → Fixed, etc).

Releases · 1

v1.0.0

RELEASE_NOTES.mdmarkdown
# Release notes

Release notes for this project — every shipped version, what changed, and when.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.0] - 2026-10-27
Dokly

Want release notes that publish themselves?

Dokly turns this Markdown into a public release-notes page with RSS, search, and filters by version — automatically.

Try Dokly free →

What goes in a good release notes template?

A useful release notes template has three things: a clear version number (semver: MAJOR.MINOR.PATCH), a release date, and a list of changes grouped by type. This generator follows the Keep a Changelog 1.1 convention: Added / Changed / Deprecated / Removed / Fixed / Security. The same structure works whether you call it a changelog, release notes, or what's new.

Release notes vs changelog — what's the difference?

They're close cousins. Changelog is the developer-facing artifact: terse, technical, every change. Release notes are the customer-facing artifact: highlight reels, marketing voice, screenshots. The structured Markdown this tool generates works for both — strip the technical entries when you publish a customer- facing version.

Best practices

  • Write for skim-readers: lead each bullet with the verb (“Added support for...”, “Fixed crash when...”).
  • Pin breaking changes: put them at the top with a clear migration note.
  • Link to PRs and commits: paste your repo URL and the tool builds GitHub release links for you.
  • Keep an Unreleased section: use the “Mark as Unreleased” checkbox so contributors know where to add notes for the next version.

Generate from git commits

If your team writes Conventional Commits (feat:, fix:, refactor:), paste git log --oneline v1.0.0..HEAD into the import box. The tool auto-classifies each line into the right bucket.

Need a different shape? Two more templates, plus Word

The Output format picker above switches this generator between the Keep a Changelog developer format, a GitHub release, and a Slack/plain-text internal post — same entries, three shapes. For the two this tool doesn't build (an end-user changelog with a screenshot, a hotfix note with severity and affected versions) or a Word / .docx-friendly version, the release notes template guide has copy-paste samples plus a workflow for keeping all five shipping.