changelog-generator

Use git log with a range between two tags, such as git log --oneline v1.0.0..HEAD, to list commits since the last release. Then group the messages by type, such as features, fixes, and breaking changes, into a formatted changelog.

Follow the Conventional Commits standard where prefixes like feat, fix, and BREAKING CHANGE indicate the change type. Map each prefix to a changelog section so readers can quickly scan what changed in the release.

Yes, changelog generation can run as a CI step that reads commits since the previous tag and appends them to the project changelog file. This keeps release documentation current without manual editing before each release.

The Keep a Changelog convention is a widely used format that groups entries by version and date with sections like Added, Changed, Fixed, and Removed. It pairs well with Semantic Versioning and Conventional Commits.

Missing entries usually happen when the tag range is wrong or commits were made on unmerged branches. Verify the correct start and end tags with git tag and ensure the target branch contains all relevant commits.