write-changelog-entry

You can generate release notes by compiling merged pull requests and commits since the last release tag, grouping them into changelog categories, and inserting the new entry under the [Unreleased] section in CHANGELOG.md.

Semantic versioning is applied by classifying changes into feat, fix, perf, refactor, test, chore, or docs categories, then proposing the appropriate vMAJOR.MINOR.PATCH increment based on the highest impact change type found.

Yes, you can safely update CHANGELOG.md by inserting the new release entry directly under the Unreleased section while preserving all existing content and never modifying previously documented releases.

The best way to suggest a version number is by analyzing the git log for conventional commit types like feat or fix, classifying the changes, and proposing a semantic version bump that requires explicit confirmation before applying.

Yes, generating a changelog entry requires explicit version confirmation before applying the update, ensuring the proposed semantic version is reviewed and approved prior to modifying the CHANGELOG.md file.

The changelog generator ignores style and revert changes to maintain a concise, user-facing release history, filtering out non-functional modifications that do not impact the semantic versioning classification or end users.