Merging this PR will not alter performance

✅ 59 untouched benchmarks

_{Comparing rodrigobnogueira:dynamic-ports-finish (4888fa8) with master (2d03bc4)}

CHANGES.rst aren't supposed to be edited in PRs, nor manually. It's updated as a part of the release process by a tool called Towncrier.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.78%. Comparing base (2d03bc4) to head (4888fa8).
⚠️ Report is 4 commits behind head on master.
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master   #12167   +/-   ##
=======================================
  Coverage   98.78%   98.78%           
=======================================
  Files         128      128           
  Lines       45327    45348   +21     
  Branches     2405     2407    +2     
=======================================
+ Hits        44777    44798   +21     
  Misses        390      390           
  Partials      160      160           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Backport to 3.14: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply b08d909 on top of patchback/backports/3.14/b08d909a0cb303498513be6916ea4e8a50792f04/pr-12167

Backporting merged PR #12167 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.14/b08d909a0cb303498513be6916ea4e8a50792f04/pr-12167 upstream/3.14

4. Now, cherry-pick PR feat: Add dynamic port binding to TCPSite #12167 contents into that branch:

   $ git cherry-pick -x b08d909a0cb303498513be6916ea4e8a50792f04

   If it'll yell at you with something like fatal: Commit b08d909a0cb303498513be6916ea4e8a50792f04 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x b08d909a0cb303498513be6916ea4e8a50792f04

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR feat: Add dynamic port binding to TCPSite #12167 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.14/b08d909a0cb303498513be6916ea4e8a50792f04/pr-12167

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.