Skip to content

Conversation

@abidlabs
Copy link
Member

In #12268, we pinned the version of pydantic to be a very narrow range. I believe that this is leading to CI failures in https://github.com/axolotl-ai-cloud/axolotl/actions/runs/20280132253/job/58280789765?pr=3253, which is preventing axolotl from upgrading to Gradio 6.0.

In this PR, I relax the pydantic dependency for base gradio and only restrict it for gradio[mcp] where it is actually needed.

@gradio-pr-bot
Copy link
Collaborator

gradio-pr-bot commented Dec 18, 2025

🪼 branch checks and previews

Name Status URL
Spaces ready! Spaces preview
🦄 Changes detected! Details

Install Gradio from this PR

pip install https://gradio-pypi-previews.s3.amazonaws.com/466de51d5dc987d34aee6f8990e5e54164625725/gradio-6.1.0-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@466de51d5dc987d34aee6f8990e5e54164625725#subdirectory=client/python"

Install Gradio JS Client from this PR

npm install https://gradio-npm-previews.s3.amazonaws.com/466de51d5dc987d34aee6f8990e5e54164625725/gradio-client-2.0.0.tgz

@gradio-pr-bot
Copy link
Collaborator

gradio-pr-bot commented Dec 18, 2025

🦄 change detected

This Pull Request includes changes to the following packages.

Package Version
gradio patch

  • Relax version of pydantic dependency in base gradio

‼️ Changeset not approved. Ensure the version bump is appropriate for all packages before approving.

  • Maintainers can approve the changeset by checking this checkbox.

Something isn't right?

  • Maintainers can change the version label to modify the version bump.
  • If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

requirements.txt Outdated
pandas>=1.0,<3.0
pillow>=8.0,<13.0
pydantic>=2.11.10,<=2.12.4
pydantic>=2.0,<=2.12.5
Copy link
Collaborator

@freddyaboulton freddyaboulton Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we do >=2.0,<3.0 here and keep it narrow in mcp?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given how often pydantic releases breaking changes, which causes all Spaces that restart to break, imo it's better to pin

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually that's a good point since we install gradio[mcp] on all Spaces anyways

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will relax more

Copy link
Collaborator

@freddyaboulton freddyaboulton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet thanks @abidlabs !

@freddyaboulton freddyaboulton merged commit c06ded8 into main Dec 18, 2025
20 of 21 checks passed
@freddyaboulton freddyaboulton deleted the relax-reqs branch December 18, 2025 22:13
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.

4 participants