changelog-keepachangelog-update

You can automatically update a CHANGELOG.md file by collecting evidence from git status and diffs, mapping those changes to predefined categories, and inserting them into the Unreleased section without fabricating details.

The Keep a Changelog format organizes release notes into standardized categories like Added, Changed, Fixed, Removed, Security, and Deprecated, ensuring a consistent structure for tracking project changes.

Yes, you can update release notes in a monorepo by specifying an explicit changelog path, allowing the tool to locate and update the correct CHANGELOG.md file within your nested project structure.

Mapping git diffs to changelog categories involves analyzing the current repository changes, categorizing them as Added, Changed, Fixed, or Removed, and updating the Unreleased section based solely on that evidence.

If the CHANGELOG.md file is missing, the update process can handle the absence by creating the necessary structure, verifying links and consistency to maintain the Keep a Changelog standard.

Yes, the changelog update process verifies the document's structure, links, and consistency after mapping repository changes, ensuring the final CHANGELOG.md adheres to the Keep a Changelog 1.0.0 standard.