aglinxinyuan commented on PR #6228: URL: https://github.com/apache/texera/pull/6228#issuecomment-4910034237
Pushed a follow-up so this can actually resolve — aiobotocore 3.7.0 can't land alone. `s3fs==2025.9.0` pins `aiobotocore<3.0.0`, and 3.7.0 requires `botocore>=1.42.90,<1.43.1`, so `uv` fails with "No solution found" (which is why every pyamber/amber-integration/Bench leg was red at the install step). Bumped the coupled family together: - `s3fs` 2025.9.0 → 2026.6.0 (accepts aiobotocore 3.x; pins `fsspec` 2026.6.0) - `botocore` / `boto3` 1.41.5 → 1.42.90 …and synced `amber/LICENSE-binary-python` for the direct deps plus the transitive members the bump pulls (`fsspec` 2026.6.0, `s3transfer` 0.16.1, `wrapt` 1.17.3 → 2.2.2 — aiobotocore 3.x relaxes its cap to `wrapt<3`). Resolution verified with `uv pip compile` across Python 3.10–3.13 and against the binary-license check. Note: since this is a manual push, Dependabot will stop managing the branch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
