changelog-automation

Use conventional commits with a tool like standard-version, semantic-release, or git-cliff to parse commit types and generate a Keep a Changelog-formatted file. Run standard-version locally or semantic-release in CI to bump versions and update CHANGELOG.md automatically.

standard-version runs locally or on demand, bumping versions and generating changelogs with manual control over releases. semantic-release runs fully automated in CI, analyzing commits on every push to main and publishing releases without human intervention.

Install commitlint with the conventional config and add a husky commit-msg hook that runs commitlint on every commit message. This rejects commits that do not follow the type(scope): description format before they enter history.

Yes, use commitizen with the cz_conventional_commits plugin configured in pyproject.toml. Running cz bump --changelog updates the version, tags the release, and appends new entries to the changelog based on commit history.

Avoid automation when the project has no release process or versioning, when you only need a one-time manual release note, or when commit history is unreliable. Generated changelogs depend on consistent, well-formed commit messages.