release-change-analyzer

To analyze unpublished code changes, compare your current HEAD with the latest published version to categorize real code differences into features, fixes, refactoring, and breaking changes for accurate release notes.

Determining the correct version bump involves categorizing actual code differences since the last release, which then allows you to recommend appropriate major, minor, or patch version increments based on the detected change types.

Code diff analysis works by comparing actual code differences between the current HEAD and the latest published version, rather than relying solely on commit messages, ensuring accurate identification of real changes.

Yes, you can automatically categorize git changes by analyzing the real code diff, which groups modifications into features, fixes, refactoring, and breaking changes to simplify release management.

You need a major version bump when the code diff analysis identifies breaking changes, whereas minor bumps correspond to new features and patch updates apply to fixes, directly mapping change types to semantic versioning.