Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.95%. Comparing base (1aef5d7) to head (61ca425).
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master   #12643   +/-   ##
=======================================
  Coverage   98.95%   98.95%           
=======================================
  Files         131      131           
  Lines       46476    46476           
  Branches     2410     2410           
=======================================
  Hits        45988    45988           
  Misses        366      366           
  Partials      122      122           

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

Merging this PR will not alter performance

✅ 68 untouched benchmarks
⏩ 72 skipped benchmarks¹

_{Comparing bdraco:ci-combine-pip-install (61ca425) with master (1aef5d7)}

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

❌ Failed to cleanly apply 348f0a1 on top of patchback/backports/3.13/348f0a1ed2887662822a44ca0f6ec0668aa292da/pr-12643

Backporting merged PR #12643 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.13/348f0a1ed2887662822a44ca0f6ec0668aa292da/pr-12643 upstream/3.13

4. Now, cherry-pick PR Combine build-tool update and dependency install into one CI step per job #12643 contents into that branch:

   $ git cherry-pick -x 348f0a1ed2887662822a44ca0f6ec0668aa292da

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

   $ git cherry-pick -m1 -x 348f0a1ed2887662822a44ca0f6ec0668aa292da

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Combine build-tool update and dependency install into one CI step per job #12643 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.13/348f0a1ed2887662822a44ca0f6ec0668aa292da/pr-12643

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.

Backport to 3.14: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.14/348f0a1ed2887662822a44ca0f6ec0668aa292da/pr-12643

Backported as #12645

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