- Install GH CLI.
- Install
gh-changelog- Ensure the
.changelog.ymlfile is in the root of the repository:--- file_name: CHANGELOG.md.new excluded_labels: - maintenance - dependencies sections: added: - feature - new feature changed: - backwards-incompatible - depricated fixed: - bug - bugfix - enhancement - fix - fixed skip_entries_without_label: false show_unreleased: true check_for_updates: true logger: console
- Ensure the
- Pull latest data from the
origin - Create new branch and name it accordingly (e.g.
docs/Update_CHANGELOG_with_<latest_version_tag>). - Run
gh changelog new --from-version <previous_version_tag> --next-version <latest_version_tag>to generate CHANGELOG since the<previous_version_tag>to<latest_version_tag>. - Open
CHANGELOG.md.new, re-arrange log entries to improve readability if applicable and copy everything under theThe format is based on […]line (release version(s) with description of changes). - Open
CHANGELOG.mdand paste copied data right underThe format is based on […]line (keep empty line between this line and pasted data). - Push your changes using conventional commit messages like
docs: Update CHANGELOG with `<latest_version_tag>`, create PR and have someone from CODEOWNERS review and approve it.