release-notes

Release notes can be drafted automatically from Git history between two refs—tags, SHAs, or branches. Provide a version, date, and range like `from_ref..to_ref`; the tool parses commits and first-parent merges, categorizes changes, and outputs ready-to-paste Markdown with breaking changes, features, fixes, and upgrade guidance.

Yes. The tool categorizes Git commits into highlights, breaking changes, features, fixes, performance improvements, security updates, deprecations, docs, and dependencies. It identifies breaking changes and migrations automatically, then generates Markdown with structured sections for each category.

Generated release notes include categorized changes, breaking changes with migration steps, upgrade and rollback instructions, feature summaries, fixes, security and performance updates, dependency changes, and documentation updates—all formatted in consistent, scannable Markdown ready to publish.

No. The tool applies a stable template and outputs release notes as ready-to-paste Markdown. You provide the version, date, and Git range; the tool handles parsing, categorization, and formatting to meet functional requirements for end users, developers, and internal ops.

The tool handles any release range defined by Git tags, SHAs, or branches. It parses first-parent merges and commits, supports complex scenarios like multi-branch releases, and generates notes suitable for major/minor/patch versions with appropriate breaking change and upgrade guidance.

The tool processes Git history between any two refs, making it adaptable to monorepos, microservices, or single-repo releases. Range-based filtering by ref lets you target specific branches or tags across your Git structure, though filtering by service or package requires custom upstream parsing.