Skip to content

docs: move version-bump default into release procedure - #3

Merged
softmaxe merged 1 commit into
mainfrom
claude/code-review-756336
Oct 12, 2026
Merged

softmaxe merged 1 commit into
mainfrom
claude/code-review-756336

Conversation

@softmaxe

Copy link
Copy Markdown
Owner

Summary

The version-bump default now lives only in step 1 of docs/agents/merge-and-release.md; AGENTS.md just points there.

choose next version
  owner names one            -> use it
  base = latest release tag
  VERSION already ahead      -> release VERSION as is
  owner asks to bump, no ver -> patch + 1 of tag (v0.0.9 -> 0.0.10)
                                note if commits have breaking/feat
  otherwise                  -> SemVer from commits since tag

Evidence

Docs-only change. Walkthrough of the cases the old rule got wrong:

  • Before: VERSION = 0.0.2 merged but untagged, owner says "bump" → 0.0.3 (0.0.2 never released). VERSION = 0.0.9 + "add 0.0.1" → could read as 0.1.0. Release doc step 1 still said SemVer, contradicting AGENTS.md.
    After: untagged 0.0.2 is released as is; 0.0.9 → 0.0.10; one rule in one file.

Merge Danger

Door: two-way

Blast Radius: agent-docs

Only changes how agents pick a release version; no code or workflow changes.

Count from the latest release tag instead of the Makefile VERSION, so an
untagged VERSION is released rather than skipped. Phrase the default as a
patch increment, flag commits that SemVer would bump higher, and keep the
rule in one place that AGENTS.md points to.
@softmaxe
softmaxe merged commit 1d6cd70 into main Oct 12, 2026
3 checks passed
@softmaxe
softmaxe deleted the claude/code-review-756336 branch October 12, 2026 05:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant