release version 0.10.0

[davidism]

This is the standard release process for Pallets projects. Create a PR updating the version and release date. This will show that the tests pass. Add the PR to the milestone. Create and push a tag for the version:

$ git tag -am 'release version 0.10.0' 0.10.0
$ git push origin 0.10.0

This will start the publish workflow in the PR. The sdist and wheel will be created and added to a draft GitHub release page. Edit the draft to check that the filenames look correct, and add any notes about the release.

The "publish-pypi" check will be pending. Once you are sure everything looks good. Click into it, and click the "Review pending deployments" link, which will give you a choice to approve uploading to PyPI. After doing so, merge the PR, publish the release page, and close the milestone.

Only members with the publish permission and core Pallets maintainers may approve the upload. PyPI's trusted publishing system is used so that no person needs direct access to PyPI.

[davidism]

This is the one place we need to use "create merge commit" and not "squash and merge", otherwise the tag will be pointing to a different commit than what gets into main.