changelog-writer

Automate changelog generation by parsing git commit history to identify changes per module, writing enterprise-style and per-module changelog files, and updating version files automatically based on a defined hierarchy.

Module version bumping works by intelligently updating versions according to a defined hierarchy from core to framework, plugins, and transports, ensuring dependency cascades are managed correctly across the release.

Yes, you can credit external contributors automatically by extracting author information from git commit history during the changelog generation process to identify and attribute outside contributors.

The best way to manage per-module changelogs is to parse git history, handle dependency cascades across the module hierarchy, and automatically write both enterprise-style and individual module changelog files while updating version files.

Automated changelog writing supports enterprise-style formats by generating structured changelog files that document changes per module and update version files according to the project's defined hierarchy.

You need to follow a specific module hierarchy—core, framework, plugins, transports—to ensure dependency cascades are handled correctly and version updates propagate properly across all affected modules.