semantic versioning
Semantic versioning communicates compatibility of a declared public API.
Use this when A library release needs a version that reflects its effect on consumers.
without the term
“I'm publishing a new version of our library. I removed a parameter and added a function. What version number should it be so people's code doesn't break unexpectedly?”
with the term · How do you ask a model for semantic versioning?
Review this release against its public API and choose the semantic version. Verify existing consumers and document any incompatible behavior.
What is semantic versioning?
In major.minor.patch, the major number changes for incompatible API changes, the minor for compatible additions, and the patch for compatible fixes. The version only means something relative to a declared public API.
Why does semantic versioning matter when vibe coding?
A small code diff can still require a breaking release.
How do you do semantic versioning?
Identify the public contract and evaluate compatibility before choosing the version.
What goes wrong with semantic versioning?
Assuming version numbers prove compatibility without checking actual consumers.