EnvGap
New JSON Schema Requirement Bumps with LiteLLM
envgap__modelcontextprotocol__python-sdk-1029
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
4b659639f7120dce0e37108b6858b6fdba463660- Manifest
pyproject.toml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
modelcontextprotocol/python-sdk #1029 · read the original issue
### Initial Checks
- [x] I confirm that I'm using the latest version of MCP Python SDK
- [x] I confirm that I searched for my issue in https://github.com/modelcontextprotocol/python-sdk/issues before opening this issue
### Description
On this commit,
https://github.com/modelcontextprotocol/python-sdk/commit/c8bbfc034d5cb876d6b91185cf02da2af6fb8b44#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R34
A new dependency was added `"jsonschema==4.20.0"` authored by @bhosmer-ant
The issue is the hard req on 4.20.0 bumps with LiteLLM
I don't see any notes in the PR that 4.20.0 precisely needs to be used. Changing it to >= anecdotally works in my case.
LiteLLM is a pretty popular package, would be nice to maintain compatibility.
```
The conflict is caused by:
mcp 1.9.5.dev23+c8bbfc0 depends on jsonschema==4.20.0
litellm 1.73.1 depends on jsonschema<5.0.0 and >=4.22.0
litellm 1.73.0 depends on jsonschema<5.0.0 and >=4.22.0
litellm 1.72.9 depends on jsonschema<5.0.0 and >=4.22.0
```
It goes on like this back to 1.72.0 released may 31, at least.
### Example Code
```Python
```
### Python & MCP Python SDK
```Text
Python 3.11
mcp 1.9.5.dev23+c8bbfc0
```04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]