Release Process¶
Release tag schema¶
Release tags should use the vX.Y.Z schema, for example v7.46.1.
The leading v is required for new release tags.
Older releases used REL_X_Y_Z-style tags (for example REL_7_45_7).
These historical tags are kept unchanged and continue to be referenced
from the changelog. New releases no longer get a REL_X_Y_Z tag.
Release workflow¶
Releases are made by the Release workflow
(.github/workflows/cibuildwheel.yml), run manually from the Actions tab
with one of these modes:
build-onlyBuild the sdist and wheels, nothing else.
testpypiBuild, then publish to TestPyPI.
releaseCheck that the version in
setup.py,doc/conf.py,ChangeLogandRELEASE-NOTES.rstagree and that the release does not exist yet, then create a draft GitHub Release whose notes are the summary fromRELEASE-NOTES.rstfollowed by theChangeLogentries. The sdist, wheels and documentation are built in parallel, and the documentation tarball is attached to the draft.The run then waits for approval of the
pypienvironment. Review the draft release and the build artifacts, then approve the deployment: the wheels and sdist are published to PyPI and the GitHub Release is published, which creates thevX.Y.Ztag at the commit that was built. If the run is rejected instead, delete the draft release by hand.
The release notes can be previewed locally with scripts/release-notes.
Release checklist¶
Ensure changelog is up to date with commits in master.
Run
scripts/update-authorsand review the updated AUTHORS file.Run
git shortlog v<previous release>...and add new contributors missed by the authors script to AUTHORS.Run
check-manifest(from PyPI) and check that none of the listed files should be in MANIFEST.in.Make sure GitHub Actions is green for master.
Create a release branch from master.
Update version numbers in: - Changelog (also record release date) - doc/conf.py - setup.py
Draft release notes, add to RELEASE-NOTES.rst.
Push release branch to GitHub.
Run the Release workflow on the release branch in
build-onlyortestpypimode and fix any issues.Run the Release workflow on the release branch in
releasemode, review the draft release, and approve the deployment.Merge release branch.
Upload documentation to web site.
Update web site home page.