release-changelog

Automated changelog generation aggregates git commits, changesets, and merged PR context since the last stable tag to compile user-facing release notes into a structured changelog file. This eliminates manual compilation by discovering the version range and categorizing changes automatically.

Idempotent changelog generation safely updates existing release notes without unintended overwrites by re-evaluating the commit history and PR merges since the last stable tag. Running the process multiple times yields the same output file, preventing duplicate entries or lost manual edits.

Yes, structured release notes can be generated with predefined sections including Breaking Changes, Highlights, Improvements, Fixes, and Upgrade Guide. The changelog aggregation categorizes commit and PR context into these distinct user-facing sections automatically.

Creating CalVer-compatible changelogs involves mapping aggregated commit history and merged PR context to a calendar-versioning scheme, outputting the structured notes into a releases/vYYYY.MDD.P.md file. This aligns the changelog format directly with the dating convention of the release.

Yes, version-range discovery is supported by identifying the last stable tag and aggregating all subsequent commits, changesets, and merged PR context. This ensures the generated changelog captures the complete user-facing changes specific to that release boundary.

Duplicate changelog entries during regeneration occur when the process lacks idempotency, causing repeated commits or PR merges to be appended. An idempotent workflow prevents this by safely updating the existing file without unintended overwrites or duplicating aggregated context.