gen-changelog

To auto-generate a changelog from git branch differences, analyze the diff between your current branch and main to produce meaningful release notes, updating root and per-package CHANGELOG.md files under the Unreleased section.

Synchronizing bilingual release notes happens automatically by syncing generated changelog entries to both English and Chinese documentation files, specifically updating docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md following project conventions.

This changelog generation method updates package-specific files by detecting relevant code changes and modifying per-package CHANGELOG.md files located in the packages/ and sdks/ directories, alongside the root changelog.

Documenting breaking changes with migration guidance involves detecting specific code differences between branches and formatting those breaking changes with migration instructions directly into the generated changelog entries.

The best way to maintain consistent release notes across multiple packages is to automate changelog propagation, updating the root CHANGELOG.md and syncing per-package logs simultaneously to ensure uniform documentation across the repository.

Generating release notes without manual entry is possible by analyzing differences between your current branch and main, automatically producing formatted changelog entries and syncing them across required documentation files.