version-scheme
SolidHow the next version number is derived and what a bump touches. Load in /release step 2 or before any version edit.
AI & Automation 2,680 stars
366 forks Updated today NOASSERTION
Install
Quality Score: 81/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Version scheme
Authority: `docs/cicd/RUNBOOK.md` section 1, `scripts/release_preflight.py`
(`read_pins`, `pins_verdict`), `tests/test_release_preflight.py`.
- Scheme: `1.108.N`; a release is `N + 1`. Minor or major moves are a
human decision with a stated reason (`/release --minor|--major <reason>`).
- Derivation, printed every time: latest tag
`git for-each-ref refs/tags --sort=-v:refname --format='%(refname:short) %(creatordate:iso-strict)' | head -1` must equal
`pyproject.toml`'s `version`. Unequal means a bump is already pending
(refuse) or a tag is missing (the pipeline tags; see the runbook).
- Pin sites are ENUMERATED BY GREP for the old version
(`--include=*.json --include=*.toml --include=*.lock`), never listed
here: the list grew from two to seven and a listed copy was wrong each
time it grew. `git check-ignore` every hit; a generated file is not a
pin site. `whatsnew.json` is regenerated (current + entry), not edited.
- `git tag <name>` is DENIED in a session (the pipeline tags); the read form above is the one to use.
- `uv.lock`: only the name-scoped `version =` line; never `uv lock` to
bump (a newer local uv rewrites platform markers; CLAUDE.md).
- The pre-flight is the authority on whether the pins agree:
`uv run python scripts/release_preflight.py --version X --pins-only`.
Details
- Author
- jgravelle
- Repository
- jgravelle/jcodemunch-mcp
- Created
- 7 months ago
- Last Updated
- today
- Language
- Python
- License
- NOASSERTION
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
release-bump
Discover what version comes next — enumerate candidates from the project's own scheme (a1→a2, 0.1.9→0.1.10, 0.2.0, 0.2.0a0), confirm with the user, then cut the release with the same safe defaults as the `release-cut` skill.
2 Updated 1 months ago
tony AI & Automation Listed
release
Bump the isopod workspace version and tag a release correctly. Use whenever a change touches crates/, Cargo.toml, Cargo.lock, vendor/ or scripts/ — CI's Version guard requires a bump for any of those — or when asked to cut, tag or release a version. Also use to diagnose a failing "Version guard" job.
3 Updated 4 weeks ago
me1iissa