release-changelog

Automate changelog generation by analyzing git commits, changesets, and merged PRs to compile user-facing release notes. The process categorizes updates into standard sections like Improvements and Fixes, ensuring consistency and saving developers significant time.

Breaking change detection for release notes works by analyzing git commits and merged PR data to identify and flag changes that break existing functionality. It then categorizes these updates into a dedicated section for user awareness and clarity.

Organize release notes into predefined categories by analyzing git commits and changesets to group updates into standard sections like Breaking Changes, Highlights, Improvements, and Fixes, ensuring user clarity and consistent documentation.

Yes, you can generate a stable release changelog without overwriting an existing file. The process ensures idempotency by checking for existing changelog files before generation, preventing duplicate or overwritten release documentation.

Draft a release markdown file by analyzing git commits, changesets, and merged PRs since the last stable release. This summarizes all user-impacting changes and categorizes them into sections like Highlights and Fixes for the new version.

You do not strictly need changesets to generate user-facing release documentation, as the process can analyze git commits and merged PRs. However, incorporating changesets alongside commit data provides a more comprehensive summary of user-impacting changes.