Release 2.4.0

[illia-v]

• Draft a social media announcement
• 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.
    export VERSION=<X.Y.Z>
    export REMOTE=origin
    git checkout main
    git pull $REMOTE main
    git tag -s -a "$VERSION" -m "Release: $VERSION"
    git push $REMOTE --tags
    

• The tag will trigger 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 and one .tar.gz. Update the GitHub
  release to have the content of the release's changelog and any ongoing announcements.
• Announce on:
  • Social media
  • Discord
  • Open Collective
• Check Tidelift security maintenance plan is still correct
• If this was a 1.26.x release, add changelog to the main branch

[sethmlarson]

LGTM!

[sethmlarson]

Our macOS CI tests are suddenly failing though, I'm curious about that?

[illia-v]

Our macOS CI tests are suddenly failing though, I'm curious about that?

Yeah, I noticed this today too

Difference between one of the last successful runs and a failing one is changed macOS from 15.3.2 24D81 to 15.4 24E248

[illia-v]

Newer memray seems to fix the issue #3589