Conventional Changelog review
A flexible open-source CLI/API for convention-driven Markdown changelogs.
Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026
Conventional Changelog is an open-source Node.js toolkit for generating CHANGELOG.md files from Git metadata. It suits teams and individual developers that want changelog generation inside release workflows rather than through a hosted dashboard. The CLI and JavaScript API parse convention-based commits, group entries into sections such as features and bug fixes, and can link entries to commits and releases. Deployment is self-hosted through a command-line tool available on Windows, macOS, and Linux.
Customization is the main strength. Conventional Commits and Angular presets provide established parsing rules, while configurable templates, context, input files, and output files let teams shape the generated Markdown. Preview, append, range, and unreleased modes support different release stages, and monorepo tag-prefix and commit-path options address repositories with multiple package paths. Companion packages add parsing, filtering, writing, and Git client building blocks, plus recommendations for major, minor, or patch version bumps.
This toolkit fits teams that already manage releases in Git and want control over how commit history becomes release documentation. Its CLI deployment and JavaScript API make it suitable for scripts, pipelines, and custom tooling, while the documentation support channel keeps the operating model lightweight. Teams seeking a hosted interface, non-Markdown outputs, or changelog generation without convention-based Git commits may prefer another type of product. Choose Conventional Changelog when repository-native customization matters more than a managed service.
Conventional Changelog pros and cons
- Where it wins
- CLI and JavaScript API support automation and custom workflows
- Templates, presets, contexts, and output files are configurable
- Monorepo paths, release ranges, previews, and bump recommendations included
- Where it doesn't
- Requires Git metadata and convention-based commit messages
- Output is centered on Markdown CHANGELOG.md files
- Support is documentation-based rather than a hosted service
Conventional Changelog fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update