docs(claude): adopt strict semver for releases#274
Merged
Conversation
…3.x patch cadence) 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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VtjoJttCvBY4dzCoE4f9vP
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the release-versioning convention in
CLAUDE.md's Workflow section: strict semver computed from conventional-commit subjects since the last tag —feat→ minor,fix/perf/refactor/chore/docs/ci/build→ patch,!/BREAKING CHANGE→ major (pre-1.0: breaking → minor).Retires the old rolling 0.3.x patch-per-release cadence (…v0.3.110/111/112 all shipped
feats as patch bumps). Going forward the version bump is computed strictly — the/deployskill reads this — so the next release carrying anyfeatafter v0.3.112 is v0.4.0, not v0.3.113.Docs-only; no code change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VtjoJttCvBY4dzCoE4f9vP