changelog-generator 变更日志

Automate changelog generation by parsing UNRELEASED.md entries, mapping module changes to categories, and drafting a new formatted section in CHANGELOG.md. This process organizes pending updates and prepares a release-ready log automatically.

A two-stage release workflow for versioning consolidates pending updates from UNRELEASED.md into CHANGELOG.md, then updates version references across designated files and commits the release. This bridges local development tracking and remote distribution.

Update version references across project files during a release by reading the consolidated changelog, applying the new version number to designated files, and committing the changes. This ensures all documentation matches the current release.

Yes, this changelog automation works without external dependencies. It operates natively on your project's UNRELEASED.md and CHANGELOG.md files to parse changes, update version references, and push the release without requiring additional packages.

The best way to manage unreleased changes is to maintain an UNRELEASED.md file during development. The automation tool then parses this file, maps changes to categories, generates the CHANGELOG.md section, and clears the UNRELEASED.md file for the next cycle.

Your changelog workflow requires clearing UNRELEASED.md to separate development cycles. After entries are parsed and published to CHANGELOG.md, clearing the file ensures pending updates do not duplicate across subsequent version releases.