changelog-generator

To generate a changelog from Conventional Commits, parse your commit history using tag ranges or direct input to automatically categorize changes into Keep a Changelog-style sections like Added, Fixed, and Changed. The tool outputs formatted markdown or JSON entries.

Yes, you can prepend generated release notes into an existing CHANGELOG.md for CI workflows. The generator optionally inserts the newly created Keep a Changelog-style entry directly at the top of your file during the pipeline run.

Yes, the changelog generator works across monorepos and CI pipelines by converting commit streams from specific git tag ranges into sectioned changelog entries. It processes commit history from your defined ranges to produce accurate release notes.

Automating release notes from git commit history is best achieved by parsing Conventional Commits to infer semantic version bumps and categorize changes. This process converts commit streams into structured Keep a Changelog-style markdown or JSON output automatically.

Yes, you need Conventional Commits formatted messages to use this automated changelog generator effectively. The parsing logic relies on conventional commit types like feat or fix to categorize changes and infer semantic version bumps for the changelog entry.

Git commits may not categorize correctly in the generated changelog if they lack proper Conventional Commits formatting. The parser requires standard prefixes like feat, fix, or chore to accurately sort changes into Keep a Changelog sections and infer semantic bumps.