changelog-gen

You can generate release notes from git history by parsing Conventional Commits using git-cliff to produce a structured changelog. This approach automates release notes creation by mapping commit types into Added, Fixed, Changed, and Security categories.

Keep a Changelog is a format that structures release notes into standardized sections like Added, Fixed, Changed, and Security. It works with semantic versioning to organize unreleased sections and per-version changes into a consistent, human-readable format.

Yes, you can integrate changelog generation into CI pipelines to auto-generate CHANGELOG.md files. The process uses git-cliff to parse Conventional Commits and link diffs between tags, enabling fully automated release notes on every deployment.

Creating an Unreleased section involves parsing Conventional Commits that have not yet been tagged. The git-cliff tool maps these pending commits into the Keep a Changelog format, categorizing them under Added, Fixed, Changed, or Security before a release.

Changelog generation relies on Conventional Commits to accurately categorize changes into Added, Fixed, Changed, and Security sections. Without standardized commit messages, the automated parsing and semantic versioning mapping cannot accurately structure the release notes.

The best way to maintain a CHANGELOG.md is using git-cliff with Keep a Changelog formatting and semantic versioning. This automates parsing commit history, linking diffs between tags, and appending structured per-version release notes without manual compilation.