Release checklist - shapely/shapely GitHub Wiki

Checklist before starting a release:

• All wheel building infrastructure up to date? (latest Python and GEOS version)
• Check or update the copyright year on Line 15 in shapely/docs/conf.py
• Update version and date-released fields in CITATION.cff
• Add date to release notes (both in CHANGES.txt and /docs/release/2.x.rst), ensure the list is complete, and add acknowledgements (eg based on git shortlog -s 2.0.1..2.0.2)

Releasing:

• Make an empty release commit: git commit --allow-empty -m 'RLS: 2.0.0'
• Tag the commit using an annotated tag. git tag -a 2.0.0 -m "Version 2.0.0"
• Push the RLS commit git push upstream main (for bugfix release: git push upstream maint-2.0)
• Also push the tag! git push upstream --tags
• Then the github worflow will create sdist/wheel, upload to PyPI, create a GitHub release, and attach the sdist
• Manually update the GitHub release body text (with content from changelog)

Packaging:

• update on conda-forge should be done automatically once the github release is made
• PyPI is already done by workflow from GitHub actions

When branching for maintenance, we tag the next commit on main with the dev version of the future major release. For example, after branching for 2.0.x, we tag for 2.1 dev:

git tag 2.1.0.dev0 eeef37fcf398afeb6342d37b63037dc398fa1a5c
git push upstream --tags