From 426e23350eb66ea756a77075833baa0e4ad16f4a Mon Sep 17 00:00:00 2001 From: Jeff Larson Date: Sun, 26 Jul 2026 16:50:20 -0700 Subject: [PATCH] docs(claude): adopt strict semver for releases (retire the rolling 0.3.x patch cadence) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Record the release-versioning convention in the Workflow section: compute the version bump strictly from conventional-commit subjects since the last tag (feat→minor, fix/perf/refactor/chore/docs/ci/build→patch, breaking→major; pre-1.0 breaking→minor), rather than the previous rolling patch-per-release (…0.3.110/111/112 shipped feats as patch bumps). So the next release carrying a feat after v0.3.112 is v0.4.0. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01VtjoJttCvBY4dzCoE4f9vP --- CLAUDE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index d82f40f..fada742 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -26,6 +26,11 @@ that grows unbounded becomes unreadable and unreviewable; that must not recur an ## Workflow - Branch + PR; never commit directly to `main`. Merge on green CI. +- **Releases follow strict semver**, computed from the conventional-commit subjects since + the last tag: `feat` → **minor**; `fix`/`perf`/`refactor`/`chore`/`docs`/`ci`/`build` → + **patch**; `!` or `BREAKING CHANGE` → **major** (pre-1.0: breaking → minor). Do not + default to a rolling patch bump — this retires the old 0.3.x patch-per-release cadence + (e.g. the next release carrying any `feat` after v0.3.112 is **v0.4.0**, not v0.3.113). - Rust edition 2024: use `cargo add` for dependencies (don't hand-edit `Cargo.toml`); run `cargo fmt`; treat `clippy` warnings as errors; run the full test suite before declaring work complete.