Package versioning

Jump to bottom

leshy edited this page Feb 27, 2026 · 1 revision

Version format: `MAJOR.MINOR.PATCH`

MAJOR: notable breaking changes
MINOR: new features (and sometimes “risky” fixes)
PATCH: bug fixes, docs, internal refactors that don’t change behavior
Security fixes: may be released ASAP even if they don’t fit neatly (because security > version purity)

Pre-1.0 (0.x)

Before 1.0.0 expectations differ:

0.MINOR.PATCH is treated as "still stabilizing"
Breaking changes may happen in a minor bump (e.g. 0.4.2 -> 0.5.0) more freely than after 1.0
Still try to signal breakage with the left-most component you’re incrementing

Example:

0.3.1 -> 0.3.2: small fix, no API change
0.3.2 -> 0.4.0: new feature, or a breaking change during early development