changelog-generator

To generate release notes from conventional commits, you can use a tool that parses git commit ranges or stdin streams and categorizes them into Keep a Changelog sections. It automatically maps commit types like Added, Fixed, and Changed, and renders the output as a Markdown or JSON entry.

The Keep a Changelog format structures release notes into distinct sections like Added, Changed, and Fixed. For automated CI pipelines, a changelog generator can parse conventional commits, produce machine-readable JSON or Markdown output, and optionally prepend the entry to an existing CHANGELOG.md file.

Yes, you can prepend new changelog entries to an existing CHANGELOG.md file. The tool parses conventional commit messages from a specified git range, maps them to Keep a Changelog sections, and writes the rendered Markdown output directly to the top of your existing changelog.

Yes, this changelog generator handles breaking changes and commit scopes. It enforces conventional-commit formatting during parsing, correctly categorizes breaking changes into the appropriate Keep a Changelog section, and includes scopes in the rendered Markdown or JSON output.

You can enforce conventional commit formatting before generating release notes by using a dedicated linter. This validates commit messages to ensure they meet conventional-commit standards, maintaining release discipline and ensuring the generated changelog entries are accurately categorized.

Yes, you can output JSON for CI/CD pipelines instead of Markdown. The tool supports rendering parsed conventional commits as either a Markdown or JSON entry, providing machine-readable output suitable for downstream CI automation, version bumping, and standalone emission.