Quick Notes113 words
Dependency versioning strategy — quick notes
Versioning strategy — quick notes
| Scheme | Encodes | Best for |
|---|---|---|
SemVer MAJOR.MINOR.PATCH | Compatibility | Libraries — "is this upgrade safe?" |
CalVer YYYY.MM.x | Time | Distributions, datasets, currency-driven products |
| SemVer part | Meaning |
|---|---|
| MAJOR | Breaking change |
| MINOR | Backward-compatible feature |
| PATCH | Backward-compatible fix |
- Pre-release tags (
-beta.2) sort before the release. - Exact pins = reproducible but stale. Ranges = current but non-deterministic.
- Range + committed lock file is the usual answer.
Trap: a breaking change published as a PATCH — worse than no scheme, because consumers relied on the guarantee.