Open
Description
Checklist for doing a new release, copied from the last one (#1319):
- Update Changelog for new release via PR, going through closed PRs to check if they got recorded in the changelog
- Create a release using the GitHub UI. This creates the appropriate tag.
- Change the
stable
symlink in stdpopsim-docs to point to the new release (if not an alpha release) - Locally,
git fetch upstream --tags
,git checkout <name of new tag>
-
python3 -m build
(note: you need thebuild
andtwine
modules installed) -
python3 -m twine upload dist/[stuff]
for instancepython -m twine upload dist/{stdpopsim-0.2.1a1.tar.gz,stdpopsim-0.2.1a1-py3-none-any.whl}
(note: this now uses "API tokens" from PyPI possibly stored in~/.pypirc
to upload; see here for the ever-changing procedure) - check on pypi that the update actually worked
- check docs build succeeded (also check the docs URL substituting the release tag where
latest
orstable
usually is) - conda-forge will do an automatic PR in the stdpopsim-feedstock repo; winni2k says:
"The key things I checked were that the version number is correct, the SHA sum has changed, and that the build number is reset to zero. Any other problems should be caught by the automated build system."
Post-release:
- make copy of this issue for the next release
Reference: https://packaging.python.org/tutorials/packaging-projects/, tskit-dev/pyslim#292