Skip to content

Latest commit

 

History

History
25 lines (20 loc) · 1.2 KB

RELEASE.md

File metadata and controls

25 lines (20 loc) · 1.2 KB
Raw

Release workflow

PyPI

  1. Draft a new release on github with a new tag (create on publish) in the style vMajor.Minor.Patch, where Major, Minor, and Patch are integers according to semnatic versioning
  2. Use the autogenerated changelog to update CHANGELOG.md in main
  3. Update the version and release date in CITATION.cff
  4. Commit the aforementioned changes
  5. Copy the modified changelog from the file to the github release draft
  6. Release the new version on github
  7. Approve the release run in the actions tab
  8. Verify that the upload to PyPI succeeded

Conda-forge

  1. Do the PyPI release first
  2. Rebase the conda-forge-release branch on the latest release
  3. Ensure correct pyproject.toml:
    • State the version explicitly (e.g. version = "1.2.3" instead of dynamic = ["version"])
    • Comment out the openrpc dependency
    • Comment out the section (including header!) [tool.setuptools_scm]
  4. Create a tag with vMajor.Minor.Patch-cf at the head of that branch
  5. Update the conda-forge repository with the version and checksum of the tar.gz archive of that tag:
    • On windows use certUtil -hashfile pyleco-1.2.3-cf.tar.gz SHA256 (adjust the version) to generate the SHA256 hash