Skip to content

Commit ebe0a3c

Browse files
authored
[Upstream Error] Pin pydantic version <2.12.0 to avoid regression (#2591)
<!-- Thanks for opening a pull request! --> <!-- In the case this PR will resolve an issue, please replace ${GITHUB_ISSUE_ID} below with the actual Github issue id. --> <!-- Closes #${GITHUB_ISSUE_ID} --> # Rationale for this change Closes #2590 I seem to be faster than the dependabot : ). Pin pydantic version to `<2.12.0` to avoid the recent regression: pydantic/pydantic#12347. I made this an upper bound because it is unclear about the fix plan in pydantic community. Once their fix is out, we could release the upper bound and exclude affected versions only ## Are these changes tested? No dependency version update. Tested the new version in #2589 and confirmed the regression ## Are there any user-facing changes? No cc: @Fokko @kevinjqliu <!-- In the case of user-facing changes, please add the changelog label. -->
1 parent ce28e00 commit ebe0a3c

File tree

2 files changed

+2
-10
lines changed

2 files changed

+2
-10
lines changed

poetry.lock

Lines changed: 1 addition & 9 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

pyproject.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ requests = ">=2.20.0,<3.0.0"
5656
click = ">=7.1.1,<9.0.0"
5757
rich = ">=10.11.0,<15.0.0"
5858
strictyaml = ">=1.7.0,<2.0.0" # CVE-2020-14343 was fixed in 5.4.
59-
pydantic = ">=2.0,<3.0,!=2.4.0,!=2.4.1" # 2.4.0, 2.4.1 has a critical bug
59+
pydantic = ">=2.0,<3.0,!=2.4.0,!=2.4.1,<2.12.0" # 2.4.0, 2.4.1, 2.12.0 has a critical bug
6060
sortedcontainers = "2.4.0"
6161
fsspec = ">=2023.1.0"
6262
pyparsing = ">=3.1.0,<4.0.0"

0 commit comments

Comments
 (0)