changelog-writer

Automated changelog generation from git history analyzes commits to identify changes per module, writes enterprise-style and simple per-module changelog files, and updates version files automatically. It reads git history to identify module-specific changes and generates multi-format changelogs.

Version bumping for strict dependency hierarchies follows a defined order: core, framework, plugins, then transports. It intelligently bumps module versions according to this hierarchy and ensures all modules receive changelog entries, even for cascading version bumps triggered by upstream changes.

Crediting external contributors when generating release notes from GitHub PRs is supported. The changelog generation process identifies and credits external contributors based on their GitHub pull requests, ensuring proper attribution is added directly into the final changelog files.

The best way to manage release versioning for the Bifrost project is using automated changelog generation. It analyzes git history and module dependencies, bumps versions based on the core-to-transports hierarchy, and writes both enterprise-style and per-module changelog files.

You do not need to manually specify every module version when generating a release changelog. You can run the process with a target transport version like v1.5.0, and it automatically bumps the dependent module versions following the strict core-to-transports hierarchy.

Changelog entries are generated for unchanged modules to handle cascading version bumps. When an upstream module like core receives an update, downstream modules like plugins and transports must also bump their versions to reflect the new dependency, ensuring all modules have valid changelog entries.