--- name: proj-version-extended description: Extends semantic versioning with conventions for `alpha`/`beta`/`rc` pre-release numbering, OS/date build-metadata tags, and version-to-dev-stage mapping (toy, vertical slice, pre-alpha, alpha, beta, rc, stable) when_to_use: Choosing or validating a version string for a pre-release, tagged build, or dev-stage milestone. Not for the base `major.minor.patch` core format or general changelog entries metadata: version: 1.4.1 --- # Projects ## Project Semantic Version - **core:** `major.minor.patch` / `x.y.z` - pre-release: append `-` plus dot-separated identifiers, e.g. `x.y.z-alpha`, `x.y.z-alpha.2`. identifiers must use `[0-9a-z-]` only; no uppercase, no empty identifiers. - build: append `+` plus dot-separated identifiers, e.g. `x.y.z+build.1`, `x.y.z-alpha+build.1`; identifiers must use `[0-9A-Za-z-]` only ### Semantic Version Extended ##### common pre-releases - pre-releases types: `alpha`, `beta`, `rc` - first pre-release: use unnumbered form, e.g. `1.0.0-alpha`. - next pre-releases: start at `.2`, e.g. `1.0.0-alpha.2`, `1.0.0-alpha.3`, **do not use:** `1.0.0-alpha.1` - pre-release patch: e.g. `1.0.0-alpha.2.1` ##### common build metadata - `1.0.0+Win`, `1.0.0+mac`, `1.0.0+linux`: builds for different OS - `0.5.0+2026-01-01-1234`, `1.0.0-alpha.2+2026-01-01`: date / date-time builds ##### development stage examples - toy/prototypes: `0.1.z`~`0.4.z` - Vertical Slice (VS): `0.5.z`~`0.8.z` - pre-alpha: `0.9.z` - alpha: `1.0.0-alpha`, `1.0.0-alpha.2`, ~~ - beta: `1.0.0-beta`, `1.0.0-beta.2`, ~~ - Release Candidate (RC): `1.0.0-rc`, `1.0.0-rc.2` - first Stable Release: `1.0.0`