Release 2.2.1

[pquentin]

• See if all tests, including downstream, pass
• Get the release pull request approved by a CODEOWNER
• Squash merge the release pull request with message "Release <VERSION>"
• Tag with X.Y.Z, push tag on urllib3/urllib3 (not on your fork, update <REMOTE> accordingly)
  • Notice that the <VERSION> shouldn't have a v prefix (Use 1.26.6 instead of v.1.26.6)

  • # Ensure the release commit is the latest in the main branch.
    git checkout main
    git pull origin main
    git tag -s -a '<VERSION>' -m 'Release: <VERSION>'
    git push <REMOTE> --tags
    

• Execute the publish GitHub workflow. This requires a review from a maintainer.
• Ensure that all expected artifacts are added to the new GitHub release. Should
  be one .whl, one .tar.gz, and one multiple.intoto.jsonl. Update the GitHub
  release to have the content of the release's changelog.
• Announce on:
  • Twitter
  • Discord
  • OpenCollective
• Update Tidelift metadata
• If this was a 1.26.x release, add changelog to the main branch

[illia-v]

Thanks @pquentin!

[pquentin]

@illia-v mentioned that #3203 made a similar change to the one reverted in #3344, so I need to inspect it before proceeding with the release. At the very least we need to be sure that botocore will work with 2.2.1.

[nateprewitt]

Confirmed current tip of main works in botocore as expected. Looking at #3203 it's a similar change but appears to only affect the request API and test infrastructure. We aren't using either so I think it's safe to say we're unaffected. The one to request may cause similar issues for other users though.