uv init --name myproj --python 3.13
uv add aiohttp==3.12.13
# Fails
uv add aiohttp-asgi-connector==1.1.2

  × No solution found when resolving dependencies for split (python_full_version >= '3.9'
  │ and python_full_version < '4'):
  ╰─▶ Because only the following versions of aiohttp{python_full_version < '4'} are
      available:
          aiohttp{python_full_version < '4'}<=3.1.0
          aiohttp{python_full_version < '4'}==3.1.1
          aiohttp{python_full_version < '4'}==3.1.2
          ... long list of versions ...
          aiohttp{python_full_version < '4'}==3.10.10
          aiohttp{python_full_version < '4'}==3.10.11
          aiohttp{python_full_version < '4'}>3.11
      and aiohttp{python_full_version < '4'}==3.8.2 was yanked (reason: This version
      includes overly restrictive multidict upper boundary disallowing multidict v6+. The
      previous patch version didn't have that and this is now causing dependency resolution
      problems for the users who have an "incompatible" version pinned. This is not really
      necessary anymore and will be addressed in the next release v3.8.3

      https://github.com/aio-libs/aiohttp/pull/6950), we can conclude that
      aiohttp{python_full_version < '4'}>=3.1.0,<3.8.3 depends on aiohttp>=3.1.0,<=3.8.1.
      And because aiohttp-asgi-connector==1.1.2 depends on aiohttp{python_full_version <
      '4'}>=3.1.0,<3.11, we can conclude that aiohttp-asgi-connector==1.1.2 depends on one
      of:
          aiohttp>=3.1.0,<=3.8.1
          aiohttp>=3.8.3,<=3.10.11

      And because your project depends on aiohttp==3.12.13 and
      aiohttp-asgi-connector==1.1.2, we can conclude that your project's requirements are
      unsatisfiable.

      hint: Pre-releases are available for `aiohttp` in the requested range (e.g.,
      3.10.11rc0), but pre-releases weren't enabled (try: `--prerelease=allow`)
  help: If you want to add the package regardless of the failed resolution, provide the
        `--frozen` flag to skip locking and syncing.