Skip to content

docs: add version rules and release steps - #7

Merged
neo-th merged 1 commit into
mainfrom
docs/version-rules
Nov 5, 2026
Merged

neo-th merged 1 commit into
mainfrom
docs/version-rules

Conversation

@neo-th

@neo-th neo-th commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Merging to main publishes nothing: release.yml only runs on a v* tag. The striper fix merged without a tag, so no release was built.

Changes

  • AGENTS.md section 7.E now covers what MAJOR, MINOR and PATCH mean, when to release, and that v* tags publish at once and are permanent.
  • The release checklist now includes the PR, the maintainer's merge, the tag and checking the published release.
  • CLAUDE.md tells agents to flag unreleased user-facing changes and ask, rather than decide to release.

Merge order

Section 7.E says release.yml stops a release when the tag doesn't match the version files. That check is added by the v0.9.4 PR, so merge both before pushing the tag.

Testing

Docs only. scripts/verify_release.sh --quick passed, with the YAML check skipped locally because PyYAML isn't installed.

Merging to main publishes nothing, and the striper fix sat unreleased because of it. Set out what each
version part means, when to release, and that v* tags publish at once and are permanent.
@neo-th
neo-th merged commit 969bfb4 into main Nov 5, 2026
1 check passed
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