Re: [PR] fix(deps, pyamber): bump botocore to 1.41.5 with compatible boto3 & aiobotocore [texera]

["aglinxinyuan (via GitHub)" <gi...@apache.org>]

aglinxinyuan commented on PR #6182:
URL: https://github.com/apache/texera/pull/6182#issuecomment-4888222760

   Dependabot's original target — botocore 1.43.40 — isn't installable here. `aiobotocore` pins botocore tightly, and no released `aiobotocore` (even the latest 3.7.0, which caps at `<1.43.1`) supports botocore that new, so `uv` failed with `No solution found` — that's what cascaded into the pyamber, amber-integration, Bench, and Required Checks failures.
   
   Since botocore/boto3/aiobotocore are a tightly-coupled family, I bumped them together to the newest set that actually resolves while staying on the `aiobotocore` 2.x line (leaving the s3fs/fsspec Iceberg path untouched):
   
   | package | before | after |
   |---|---|---|
   | botocore | 1.40.53 | 1.41.5 |
   | boto3 | 1.40.53 | 1.41.5 |
   | aiobotocore | 2.25.1 | 2.26.0 |
   
   `amber/LICENSE-binary-python` is synced for those three plus the transitive `s3transfer` 0.14.0 → 0.15.0 that boto3 1.41.5 pulls in.
   
   Verified locally: resolves cleanly on py 3.10–3.13, the resolved tree differs from `main` by exactly these four packages, the LICENSE-binary drift check comes back clean, and a smoke test constructs botocore/boto3/aiobotocore/s3fs clients + pyiceberg's `FsspecFileIO`. Going to 1.43.x would need a major `aiobotocore` 2→3 upgrade of the Iceberg S3 stack — better as its own PR.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org