Doing a release to PyPI

Thanks to our publishing workflow, doing a new release is absolutely trivial:

• Check what the latest release is called on the release page
• Determine what type of release this is, and what the new version will be called:
  • If there are breaking, non-backward-compatible changes, this is a major release, and we bump the version by going from e.g. 3.11.0 to 4.0.0.
  • If there are new features, but these are fully backward compatible and non-breaking, this is a minor release, and we bump the version by going from e.g. 3.11.0 to 3.12.0
  • If these are just minor fixes to existing features, this is a patch release, and we bump the version by going from e.g. 3.11.0 to 3.11.1
• Finally, go to the release page and create a new release, using the new version as the tag, prefixed with a v. Make sure to describe what's in the release!

See previous releases for examples of how to tag and describe these.

That's it - everything else will be handled automatically by CI.