release-changelog

Automate release notes generation by aggregating git commit messages, changeset metadata, and merged pull request context since the last stable tag. This process compiles a structured, user-facing changelog file for your versioned software release.

Changeset metadata improves changelog versioning by providing structured context from merged PRs and commits. This allows the automation to segment changes into Breaking Changes, Highlights, Improvements, and Fixes for a consistent release file.

Generate a structured changelog file by detecting the last stable git tag and aggregating all subsequent changesets and PR context. The system outputs a single markdown file at releases/v{version}.md for manual review before publishing.

No, the changelog automation ensures idempotency by preserving existing release notes artifacts. It presents the generated file for manual review before publish, preventing accidental overwrites of previously reviewed release documentation.

Yes, you can use this to separate breaking changes and fixes. The automation segments aggregated commits and changeset metadata into distinct categories including Breaking Changes, Highlights, Improvements, and Fixes within the final changelog.

You need to provide git tag history, changeset metadata, and merged pull request context as inputs. The automation uses these inputs to detect changes since the last stable tag and outputs a single file at releases/v{version}.md.