SemVer decide

Current version + a changelog in, the next version out — by the rules, not by feel.

Inputs

• current — the current version, MAJOR.MINOR.PATCH.
• changes — a list of { type } where type is breaking | feat | fix (chore/docs/refactor count as fix-level for a release, or no bump if that's all there is).

Rules (highest wins)

• any breaking → major: bump MAJOR, reset MINOR and PATCH to 0.
• else any feat → minor: bump MINOR, reset PATCH to 0.
• else any fix (or release-worthy change) → patch: bump PATCH.
• 0.x caveat: pre-1.0, a breaking change bumps MINOR (not MAJOR) by convention — note it if it applies.

Output

{ bump: "major"|"minor"|"patch", next: "X.Y.Z" }

Pure arithmetic over the rules — the same inputs always yield the same version.