Skip to content

fix: keep locked pydantic co-installable with the HF Space runtime - #27

Merged
titusz merged 1 commit into
mainfrom
hf-space-pydantic
Aug 3, 2026
Merged

titusz merged 1 commit into
mainfrom
hf-space-pydantic

Conversation

@titusz

@titusz titusz commented Aug 3, 2026

Copy link
Copy Markdown
Member

The v0.2.2 Space deploy failed to build: the Space image installs requirements.txt alongside gradio[oauth,mcp], whose mcp extra pins pydantic<=2.12.5, conflicting with our locked pydantic==2.13.4 (ResolutionImpossible).

  • Adds a uv constraint-dependencies entry so the lock (and the exported requirements.txt the Space consumes) stays co-installable — resolves to pydantic 2.12.5. Lock/export only; published package metadata is unaffected. 149 tests pass at 100% coverage.
  • Syncs space.yml with the deployed Space config: Gradio 6.22.0 (locked version) and python_version: 3.12 (onnxruntime>=1.24 has no Python 3.10 wheels).

After merge I'll re-sync the Space from main. Note: the huggingface.yml sync workflow itself is broken (unmaintained action gets 400 from the Hub API) — issue draft with a proposed replacement is ready to file separately.

The Space image installs requirements.txt alongside gradio[oauth,mcp],
whose mcp extra pins pydantic<=2.12.5; the locked pydantic 2.13.4 made
the Space build fail with ResolutionImpossible. Constrain the uv
resolution (lock/export only - package metadata is unaffected) and
sync space.yml with the deployed Space config (Gradio 6.22.0,
Python 3.12 - onnxruntime>=1.24 has no 3.10 wheels).
@titusz
titusz merged commit e5c8f48 into main Aug 3, 2026
24 checks passed
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.

1 participant