Conventional Changelog
The facts below are what the maker publishes about Conventional Changelog, checked and dated. Our editors have not written about it yet.
The facts
Each one read from Conventional Changelog's own pages, with the date it was checked.
What it does
- Changelog behavior
- The CLI example generates from commits since the last matching semver tag and does not overwrite prior changelogs.checked 14 Nov 2026
- CLI and API
- The product provides a command-line tool and JavaScript API.checked 14 Nov 2026
- Commit conventions
- A commit convention is recommended for best tokenization and flexible output, but Angular convention is not required.checked 14 Nov 2026
- Companion integrations
- The documentation recommends Commitlint for checking messages and Commitizen for an interactive commit-message prompt.checked 14 Nov 2026
- Customization
- Users can customize commit types, sections, and links.checked 14 Nov 2026
- License
- The package README states that conventional-changelog is MIT licensed.checked 14 Nov 2026
- Organized entries
- The tool groups commits into sections such as Features and Bug Fixes and links entries to commits and releases.checked 14 Nov 2026
- Package installation
- The package README documents installation through pnpm, yarn, or npm.checked 14 Nov 2026
- Presets
- Presets encode commit conventions, including Conventional Commits and Angular.checked 14 Nov 2026
- Purpose
- Conventional Changelog generates a CHANGELOG.md from git metadata and commit messages that follow a convention.checked 14 Nov 2026
- Release automation
- The changelog tool handles changelogs and version recommendations; automating version bumps, tagging, and publishing requires companion tooling.checked 14 Nov 2026
- Version bump recommendations
- A companion tool recommends whether the next release should be major, minor, or patch.checked 14 Nov 2026
Where it runs
- Monorepos
- The related simple-release-action supports monorepos and is built on this project.checked 14 Nov 2026
