aioboto3 15.5.0 pins aiobotocore[boto3] == 2.25.1 exactly, which transitively caps boto3 < 1.40.62. That blocks consumers from picking up newer boto3 releases.
aiobotocore 2.25.2 was already released and widens the bound to boto3 < 1.40.71 (and there's a 2.26.0 allowing the 1.41.x line).
A new aioboto3 patch release that bumps the pin to aiobotocore[boto3] == 2.25.2 (or relaxes to a
range like >=2.25.2,<2.26) would unblock everyone downstream.
Current state:
aioboto3 15.5.0 → aiobotocore[boto3] == 2.25.1 → boto3 >=1.40.46,<1.40.62
Requested:
- An aioboto3 release pinning
aiobotocore[boto3] == 2.25.2 (or a small range), so boto3 1.40.68 (and similar) resolves.
Why I'm asking: boto3 1.40.68 ships an identitystore API update that adds a UserStatus field (plus Birthdate, Website, Photos, and CreatedAt/By / UpdatedAt/By metadata) on the IdentityStore User APIs — we need this to read the
user status from AWS Identity Center. Without an aioboto3 release that allows aiobotocore 2.25.2+, there's no clean way to get boto3 1.40.68 through the resolver.
Thanks!
aioboto315.5.0 pinsaiobotocore[boto3] == 2.25.1exactly, which transitively capsboto3 < 1.40.62. That blocks consumers from picking up newer boto3 releases.aiobotocore 2.25.2was already released and widens the bound toboto3 < 1.40.71(and there's a 2.26.0 allowing the 1.41.x line).A new aioboto3 patch release that bumps the pin to
aiobotocore[boto3] == 2.25.2(or relaxes to arange like >=2.25.2,<2.26) would unblock everyone downstream.
Current state:
aioboto3 15.5.0→aiobotocore[boto3] == 2.25.1→boto3 >=1.40.46,<1.40.62Requested:
aiobotocore[boto3] == 2.25.2(or a small range), soboto3 1.40.68(and similar) resolves.Why I'm asking:
boto3 1.40.68ships an identitystore API update that adds a UserStatus field (plus Birthdate, Website, Photos, and CreatedAt/By / UpdatedAt/By metadata) on the IdentityStore User APIs — we need this to read theuser status from AWS Identity Center. Without an aioboto3 release that allows aiobotocore 2.25.2+, there's no clean way to get
boto3 1.40.68through the resolver.Thanks!