release-notes

Generate release notes by aggregating commits, pull requests, and fixed issues since a chosen base release. The tool compiles these Git-based changes into a structured Markdown document and saves it to release-notes/v{version}.md.

Yes, generating a changelog automatically tags the repository with the new version and pushes the changes. This happens after the tool collects git log data and formats it into a standardized Markdown document.

Yes, release notes generation supports normalization of version formats. It checks for existing tags before applying the new version tag to the repository to prevent conflicts during the aggregation process.

Include breaking changes and upgrade guidance by collecting changelog data from git logs and issues, then formatting the results into a standardized Markdown document. The output incorporates environment considerations for operators alongside the structured release notes.

Automated release notes generation checks for existing tags before applying a new version tag to the repository. It aggregates commits, PRs, and issues since the base release to ensure no duplicate versioning occurs when pushing changes.