From 7e3804d0b5f33d05f9cf45868cdaeaf3a3745bf0 Mon Sep 17 00:00:00 2001
From: Olivier Desenfans <desenfans.olivier@gmail.com>
Date: Thu, 11 Jun 2026 18:14:26 +0200
Subject: [PATCH] fix(ci): pin aiohttp<3.13 in the testing env

aiohttp 3.13 changed ClientResponse.__init__ (new stream_writer kwarg)
and aioresponses, including the latest 0.7.8, cannot mock it. This has
been failing the vm client tests (23 of them) in CI since the resolver
started picking aiohttp 3.13+, including the nightly runs on main. The
pin is test-only; the runtime requirement stays aiohttp>=3.8.3.
---
 pyproject.toml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/pyproject.toml b/pyproject.toml
index e52d84be..13ee595d 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -148,6 +148,9 @@ envs.testing.dependencies = [
   "pytest-mock==3.12.0",
   "pytest-asyncio==0.23.5",
   "pytest-aiohttp==1.0.5",
+  # aiohttp 3.13 changed ClientResponse.__init__ (new stream_writer kwarg),
+  # which aioresponses (up to 0.7.8) cannot mock. Test-only pin.
+  "aiohttp<3.13",
   "aioresponses==0.7.6",
   "fastapi",
   "httpx",