generate_release_note

Generate bilingual release notes by analyzing the git diff between the previous version tag and current main branch, producing structured documentation files under docs/en/release_notes and docs/ja/release_notes.

Automated release note generation classifies user-facing changes from the git diff into categories like breaking changes, new features, internal changes, bug fixes, and documentation, avoiding bias from raw commit messages.

Automate EN and JA changelog creation by deriving structured release notes from git history, ensuring consistent section ordering, pip-install header formatting, and correct PR and tutorial link formatting across both languages.

Yes, generating versioned release note files under docs/en/release_notes and docs/ja/release_notes automatically updates the corresponding myst index files to maintain documentation index consistency.

Ensure consistent formatting by reusing the most recent release note’s conventions for layout and phrasing, enforcing mandatory section ordering, and applying verified snippet output conventions for PR references.

Automated release note generation requires valid previous and current version tags, such as v0.11.1 and v0.12.0, to accurately calculate the git diff and apply the correct version numbering to the output files.