Skip to content

fix(deps): declare jsonschema as a runtime dependency - #548

Merged
chris-dare-dev merged 2 commits into
mainfrom
claude/declare-jsonschema
Nov 15, 2026
Merged

chris-dare-dev merged 2 commits into
mainfrom
claude/declare-jsonschema

Conversation

@chris-dare-dev

@chris-dare-dev chris-dare-dev commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

What

server/tools.py imports jsonschema at module load, to validate lean_verify's result against the schema the tool advertises. No runtime dependency declared it; it installed only because mcp requires it. The contract extra, which #547 removed, was the one place it was ever named.

This declares it explicitly at the >=4.20 floor mcp already requires, with the same kind of comment pyproject.toml gives jinja2 and python-multipart ("already a transitive dep via mcp; declared explicitly"). This is the runtime counterpart of what #377 did for httpx in the dev group.

Verification

Notes

server/tools.py imports jsonschema to validate lean_verify's result
against the schema it advertises, but no runtime dependency declared
it. It installed only because mcp requires it. The contract extra,
which #547 removes, was the one place it was ever named. Declare it
explicitly, at the >=4.20 floor mcp already requires, as the project
does for jinja2 and python-multipart.

uv.lock gains only the jsonschema lines; `uv lock --check` passes.
#547 removed the contract extra, whose jsonschema entry sat next to
the runtime one this branch adds. uv.lock keeps the runtime
requirement and drops the contract one.
@chris-dare-dev
chris-dare-dev merged commit d3c4ff0 into main Nov 15, 2026
1 check passed
@chris-dare-dev
chris-dare-dev deleted the claude/declare-jsonschema branch November 15, 2026 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants