From f98d306fd6314910dd6ce29dc22bcbcffa9bd958 Mon Sep 17 00:00:00 2001 From: owine Date: Sun, 10 May 2026 09:36:31 -0500 Subject: [PATCH] Cap boto3/botocore to <1.38 for aiobotocore compatibility The previous lower-bound-only constraints let pip resolve boto3/botocore to the newest PyPI release whenever this package is installed. Anything in the same env that uses aiobotocore then breaks, because aiobotocore pins botocore to a narrow range. In Home Assistant the symptom is Cloudflare R2, IDrive e2, and Nice G.O. failing to set up after a user opens the Hive config flow. >=1.34,<1.38 keeps pip inside what aiobotocore 2.21.x accepts. Bump it when downstream consumers move to aiobotocore 3.x. Refs: #135 --- pyproject.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 37b4e30..e94315d 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -25,8 +25,8 @@ classifiers = [ "Topic :: Software Development :: Libraries :: Python Modules", ] dependencies = [ - "boto3>=1.16.10", - "botocore>=1.19.10", + "boto3>=1.34,<1.38", + "botocore>=1.34,<1.38", "requests", "aiohttp", "pyquery",