Version Aligner FAQs

Question 1

How does it calculate the next version bump?

Accepted Answer

The skill analyzes your Git history for Conventional Commits. It detects 'feat!' or 'BREAKING CHANGE' for Major bumps, 'feat' for Minor bumps, and 'fix' for Patch bumps.

Question 2

Can it prevent breaking changes between frontend and backend services?

Accepted Answer

Yes, it performs compatibility validation by checking API contracts and dependency ranges (like package.json constraints) to identify mismatches before you release.

Question 3

Does it automate the creation of Git tags?

Accepted Answer

Yes, Version Aligner can execute the version update in your configuration files, generate markdown changelogs, and create the corresponding Git tags for your release.

Question 4

What versioning strategies does Version Aligner support?

Accepted Answer

It supports three primary strategies: Lockstep (all repos share the same version), Independent (each repo tracks its own version), and Umbrella (individual service versions mapped to a single product milestone).

Question 5

Is this skill useful for monorepos?

Accepted Answer

Absolutely. It is designed to manage version alignment both across separate repositories and between multiple packages within a single monorepo structure.

Version Aligner

Key Features

Use Cases

Version Aligner

Key Features

Use Cases