build(deps): raise pydantic floor to >=2.11#24
Closed
przemarzec wants to merge 1 commit into
Closed
Conversation
The MCP server extra (added in a follow-up) depends on the mcp SDK, which requires pydantic>=2.11. Raise the floor uniformly here so the whole stack stays on one pydantic minimum rather than carrying a per-extra exception. This is a declaration change only — no code change (already runs on >=2.12).
Contributor
Author
|
Closing — premature. v0.4.0 is being implemented as a whole on a local release branch first; this change will land via the release flow at milestone close, not as a standalone PR to dev. |
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
Raise the minimum pydantic from
>=2.9.0to>=2.11.0independencies.Why
A forthcoming optional MCP-server extra depends on the
mcpSDK, which requirespydantic>=2.11. Raising the floor uniformly keeps the whole package on one pydantic minimum instead of a per-extra exception.Impact
Verification (local)
import engravaclean.build:change → semantic-release will not bump/publish.