version-bump-cx

Automating changelog generation involves parsing git commit history since the last tag, categorizing entries by Conventional Commits patterns, and appending a date-stamped release section to CHANGELOG.md.

Syncing package versions across workspace packages requires updating version references in all package.json files, regenerating lockfiles, and refreshing documentation artifacts like openapi.yaml and llm.txt to ensure repository-wide consistency.

Yes, you can automate patch releases by applying a PATCH-only version rule, which includes a threshold-based rollover mechanism to handle large patch increments appropriately.

Version bump automation works directly with Conventional Commits by parsing patterns like breaking changes, features, and fixes from your git history to build categorized release notes.

Keeping openapi.yaml and llm.txt versions in sync involves scanning for version touchpoints across all repository files and updating documentation references alongside package.json bumps.

A limitation of patch-only version bumps is the exclusion of minor and major version increments, meaning breaking changes are documented in the changelog but do not trigger a major version update.