chore(deps): drop redundant pydantic_core pin - #362
Merged
Conversation
pydantic pins its core exactly (2.13.4 requires pydantic-core==2.46.4), nothing in this repo imports pydantic_core directly, and CI installs via plain 'pip install -r', so the resolver already determines core deterministically from pydantic's own == constraint. The explicit pin adds no reproducibility and creates a failure class: whenever pydantic-core releases without a paired stable pydantic, renovate proposes an unpaired core bump that can never resolve (see closed #338). Dropping the pin makes pydantic bumps self-contained and ends that PR class structurally.
gadievron
requested review from
dgeyshis,
shahar-davidson and
sounil
as code owners
August 27, 2026 17:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the
pydantic_core==2.46.4line fromrequirements.txt.Why
2.13.4→pydantic-core==2.46.4); nothing in the repo importspydantic_coredirectly, and CI installs with plainpip install -r— the resolver already determines the core version deterministically from pydantic's own==constraint. The explicit pin adds zero reproducibility.Verification
grep -rn pydantic_core --include='*.py'→ zero hits; GitHub code search → requirements.txt only--no-deps/--require-hashesanywhere in CI or docs;pyproject.tomldeclares onlypydantic>=2.0.0