Tags and Releases#

PyUnitWizard uses numeric Git tags without v prefix (for example 0.28.1). The public GitHub Release title/name must exactly match that version and tag; descriptions belong in the body. See the release-title rule.

Baseline policy#

  • Pre-1.0 releases follow incremental stabilization.

  • 0.19.x is a historical checkpoint line.

  • 0.20.x is the interoperability expansion line.

  • 0.21.x is the completed RC consolidation line.

  • 0.22.x and 0.23.x are post-RC hardening lines before 1.0.0.

  • 0.24.x–0.28.x continue hardening and provisional optional interfaces; 0.28.1 is the current published checkpoint.

  • 1.0.0 is a separately approved stable milestone, not a consequence of completing the historical 0.21.x RC checklist.

  • If a tag was created by mistake, do not rewrite history; continue with the next correct numeric tag.

Creating the next tag#

From main, after the full matrix, policy, release gates, and any required staged installed-package tests are green at the same commit:

git fetch origin
git switch main
git pull --ff-only origin main
python -m pytest --receptor=llm tests
make -C docs html
# replace X.Y.Z with the next version
git tag X.Y.Z
git push origin main
git push origin X.Y.Z
# After verifying the exact tag/candidate gates and prepared release notes:
gh release create X.Y.Z --verify-tag --title X.Y.Z --notes-file RELEASE_NOTES

For a staged Conda route, publishing the GitHub Release verifies the committed plan but does not rebuild the package. Promote the digest-verified staged file afterward; see devtools/conda-build/README.md. A direct route builds once on the stable release event, after its registry preflight.

Release references#