Repository navigation
docs: move version-bump default into release procedure - #3
Merged
Merged
Conversation
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.
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
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.
Summary
The version-bump default now lives only in step 1 of
docs/agents/merge-and-release.md;AGENTS.mdjust points there.Evidence
Docs-only change. Walkthrough of the cases the old rule got wrong:
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.