commit-changes

To bump package versions in a monorepo, map changed files to their corresponding package.json paths and apply patch version bumps. Downstream dependents within the package groups must also receive cascaded version bumps to maintain dependency consistency.

The correct commit subject format for multi-package changes is a single, composed subject that reflects all touched packages. It enforces project-wide commit conventions by summarizing the mapped file changes into one compliant string.

Mapping changed files to the correct package.json path requires tracing modified files back to their parent package directory. This ensures accurate versioning by isolating which specific packages in the monorepo need a version bump.

You do not need to manually update downstream dependents when bumping versions. The process automatically cascades patch version bumps to downstream dependencies across the auth and package groups within the monorepo.

You can use this monorepo commit convention tool for single-package changes. It formats commit subjects and bumps versions for individual packages just as effectively as it handles multi-package modifications.

A limitation of automating version bumps across package groups is that the process is strictly bound to the SchemaVaults Auth monorepo structure. It relies on accurate file-to-package mapping and applies only patch level bumps to affected packages.