revert: uvloop 0.22.1 → 0.21.0 in ci requirements

[Copilot]

Dependabot PR #3818 bumped uvloop from 0.21.0 → 0.22.1 as part of a multi-dependency update. This reverts only the uvloop portion, keeping all other dependency bumps from that PR intact.

Changes

• ci/requirements.in — pin back to uvloop==0.21.0
• ci/requirements.txt — replace 0.22.1 entry and its hashes with the 0.21.0 hashes from main

Original prompt

Context

PR #3818 (dependabot/pip/actions/gcp/setup/dependencies-441176d5a0 branch) is a dependabot PR that bumps 9 dependencies across 3 directories. One of those updates is uvloop from 0.21.0 to 0.22.1, which we do NOT want.

Task

Create a PR against the dependabot/pip/actions/gcp/setup/dependencies-441176d5a0 branch (NOT against main) that reverts ONLY the uvloop-related changes from PR #3818.

What needs to be reverted

1. ci/requirements.in — revert the uvloop version pin back:

   • Change uvloop==0.22.1 back to uvloop==0.21.0

2. ci/requirements.txt — this is the lock file. The uvloop entry and its hashes need to be reverted. In the current state on the dependabot branch, uvloop was bumped from 0.21.0 to 0.22.1 with new hashes. You need to:

   • Find the uvloop entry in ci/requirements.txt on the dependabot branch and change the version and hashes back to the 0.21.0 versions
   • The old uvloop==0.21.0 entry from main branch should be used as the source of truth for the hashes

   The old entry on main is:

   uvloop==0.21.0 \
       --hash=sha256:10d66943def5fcb6e7b37310eb6b5639fd2ccbc38df1177262b0640c3ca68c1f \
       --hash=sha256:67dd654b8571f2a13c4e3b23b920bd9ccdf78fa43ef0844db6871b4e3ace8fc9
   

What should NOT be changed

• actions/gcp/setup/requirements.txt — has NO uvloop changes, leave it alone
• py/deps/requirements.txt — has NO uvloop changes, leave it alone
• Any other dependency updates in ci/requirements.txt should be LEFT AS-IS (don't revert the other dependency bumps in that file)

Important notes

• The base branch for this PR MUST be dependabot/pip/actions/gcp/setup/dependencies-441176d5a0 (the head branch of PR build(deps): bump the dependencies group across 3 directories with 9 updates #3818)
• Only touch ci/requirements.in and ci/requirements.txt
• Only revert uvloop-related changes, nothing else

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: been trying various ways to stop dependabot updating without uvloop - no dice, fuck that

now please just open a pr - against this one to revert ONLY the changes to uvloop (and anything related/that needs the uvloop version change) ONLY - against that pr - it should update all req files lock files etc etc

Assistant:

Let me first examine the PR to understand what changes were made, particularly around uvloop.

Assistant: Now I have a clear picture of all the changes in PR #3818. Let me identify the uvloop-specific changes:

1. ci/requirements.in: Changes uvloop==0.21.0 → uvloop==0.22.1 — this is the only uvloop-specific .in file change
2. ci/requirements.txt: This massive lock file was regenerated and contains the uvloop version bump plus all its cascading dependency changes

The other files (actions/gcp/setup/requirements.txt and py/deps/requirements.txt) don't contain uvloop changes — they have other dependency updates (gsutil, multidict, propcache, yarl, protobuf, etc.).

So the PR to revert uvloop needs to:

• Revert ci/requirements.in to keep uvloop==0.21.0
• Revert the uvloop entry in ci/requirements.txt back to the old version/hashes

Let me check what the uvloop section looks like in the PR's ci/requirements.txt:

Assistant: Now I have a clear picture. Let me analyze the PR #3818 changes:

Files changed:

1. actions/gcp/setup/requirements.txt - updates to google-auth-httplib2, gsutil, multidict, propcache, yarl
2. ci/requirements.in - uvloop 0.21.0 → 0.22.1 ← THIS is the uvloop change
3. ci/requirements.txt - large lock file update (includes uvloop and all its transitive deps)
4. py/deps/requirements.txt - updates to aiodocker, protobuf, pytz, types-protobuf, types-pytz, yarl, setuptools

The uvloop change is ONLY in ci/requirements.in (the .in file) and ci/requirements.txt (the lock file). No other file has uvloop changes. However, the ci/requirements.txt lock file has many other changes too (massive update), so the PR needs to revert ONLY the uvloop-specific parts.

Let me create the PR:

Assistant: I've kicked off the creation of a PR against the dependabot branch (dependabot/pip/actions/gcp/setup/dependencies-441176d5a0) to revert only the uvloop changes. Specifically it will:

1. ci/requirements.in: Revert uvloop==0.22.1 → uvloop==0.21.0
2. ci/requirements.txt: Revert the uvloop entry and hashes back to the 0.21.0 versions

All other dependency updates from PR #3818 (google-auth-httplib2, gsutil, multidict, propcache, yarl, aiodocker, protobuf, pytz, setuptools, types-protobuf, types-pytz) will be left intact.

The coding agent is working on this now — you'll get a PR link shortly once it's created. This PR will target the dependabot branch so that when merged, it removes the uvloop bump while keeping everything else from the dependabot update.

This pull request was created from Copilot chat.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.