60
semver
also semantic versioning
MAJOR breaks callers. MINOR adds. PATCH fixes. The number is a promise, not a vibe.
What is semver?
Semantic versioning is MAJOR.MINOR.PATCH. Breaking an existing caller is major. A compatible addition is minor. A bugfix that keeps the contract is patch.
Why does semver matter when vibe coding?
Models bump versions at random, or publish a breaking rename as 1.0.1. Downstream vibe-coded apps then explode on install. Name semver and name what changed for callers.
How do you do semver?
Before a release, list caller-visible changes. If any name, type, or required field changed, it is major. Do not “just bump patch.”
How do you ask a model for semver?
Follow semver. This change (breaks / adds / fixes) callers, so bump (major / minor / patch). Do not renumber for taste.
What goes wrong with semver?
0.x forever so you never have to mean it. Pre-1.0 still needs a note when you break people.