Skip to content

Latest commit

 

History

History
18 lines (16 loc) · 1.48 KB

RELEASE.md

File metadata and controls

18 lines (16 loc) · 1.48 KB
Raw

Release

pycontrails is tagged and pushed to pypi through GitHub Actions.

  1. Ensure all changes to be released are committed and pushed to main.
  2. Ensure Unit tests and Doc / Notebook tests have passed on main. The Release Action will fail if these actions have not completed successfully.
  3. Review and update the CHANGELOG. Ensure the most recent entry is for the tag about to be released.
  4. Create a new release on Github. Double check that the release tag is consistent and consecutive with the previous release tag following PEP 440. This often but not always agrees with Semantic Versioning.
  5. Copy the CHANGELOG content for the release into the Description.
  6. Publish the new release. This will create a tag on main and trigger the Release Action.
  7. Confirm that the release is successfully deployed to PyPI.
  8. Confirm that the documentation is successfully deployed to py.contrails.org.