Skip to content

Latest commit

 

History

History
23 lines (17 loc) · 988 Bytes

RELEASE.rst

File metadata and controls

23 lines (17 loc) · 988 Bytes
Raw

Release process

  1. Add new entry in NEWS.rst along with changelog updates for the release.
  2. Make sure dependency versions are correct in requirements/install.txt. Also, if requirements/pyproject.toml exists make sure dependency versions match those in requirements/install.txt for matching dependencies.
  3. Run a test release build by force pushing to a temporary "deploy" branch. This triggers the release workflow to run on Github, but doesn't actually upload any of the generated files to PyPI or Github.
  4. Verify the test build looks correct and passes tests then tag the new release and push the tag. If everything works as expected, both PyPI and Github should automatically get the release files pushed to them once the action completes.
  5. At this point, it's good to remove the temporary deploy branch from the upstream repo.
  6. Make a commit bumping the package version via __version__ in the base module and push the commit.