Skip to content

Commit 5e8ca91

Browse files
authored
Merge pull request #2173 from transformerlab/fix/dependabot-boto3-patch-ignore
Pin boto3 for now until datasets gets unlocked.
2 parents 09ec49a + 754b4b8 commit 5e8ca91

1 file changed

Lines changed: 8 additions & 6 deletions

File tree

.github/dependabot.yml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,13 +119,15 @@ updates:
119119
# fails immediately on import. Revisit after refactoring the import path. See PR #2083.
120120
- dependency-name: "azure-mgmt-resource"
121121
versions: [">=25"]
122-
# boto3 1.41+ requires botocore >=1.41, which in turn requires newer aiobotocore /
123-
# s3fs / fsspec. But `datasets` is pinned to 3.x (above), which caps
124-
# fsspec at <=2025.3.0 — and the s3fs releases compatible with that fsspec cap
125-
# only support botocore <1.41. Result: boto3 >=1.41 is uninstallable until the
126-
# datasets pin is lifted. Hold boto3 at 1.40.x. See PR #2159.
122+
# boto3 patches beyond 1.40.70 are uninstallable. Each boto3 patch pins a
123+
# matching botocore patch, and aiobotocore's compatible window in the 1.40
124+
# line is botocore>=1.40.37,<1.40.71 — so boto3 1.40.71+ (and all of 1.41.x)
125+
# fall in a dead zone aiobotocore won't accept. aiobotocore is pulled in
126+
# transitively via s3fs, which is capped by fsspec, which is capped by the
127+
# `datasets` 3.x pin above. Hold boto3 at 1.40.70 until datasets is unpinned
128+
# or a newer aiobotocore covers the gap. See PR #2159, PR #2169.
127129
- dependency-name: "boto3"
128-
versions: [">=1.41"]
130+
versions: [">1.40.70"]
129131

130132
# CLI (Typer, managed with uv)
131133
- package-ecosystem: "uv"

0 commit comments

Comments
 (0)