Versions Can Have Three Parts or Four, and Agents Know Which Is Which
The kit no longer insists on four-part versions. Market-standard 0.1.0 is just as valid, and the user picks.
- Path
- changelog/2026-11-02_01.md
- Authors
- Michael Staton
- Augmented with
- Claude Code on Claude Opus 5.5
- Tags
- Context-Vigilance · Versioning
Why Care?
The market standard is three parts,
major.minor.patch
, and the skill called
four parts the one right answer. Anyone installing the kit shouldn't have to
adopt our format, but agents do need to read both correctly: the
1
in
0.1.0
is a minor, and the
1
in
0.1.0.0
is a major.
What's New?
-
Both formats are valid. The user picks and nothing enforces it.
-
Agents count the parts first, keep the format a doc or repo already uses, and never convert between them. Published packages always use three.
-
The source of epochs is credited: Anthony Fu's Epoch Semantic Versioning . His format stays at three numbers, so
1002.3.0means epoch 1, major 2, and agents can read that too.
Templates still start at
0.0.0.1
, and no existing version changed.