GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — fix: relax pydantic-core upper bound from <2.44.0 to <3 · Pull Request #23 · VapiAI/server-sdk-python

Conversation

@ghost

@ghost ghost commented May 20, 2026

Copy link
Copy Markdown

Summary

  • Relaxes pydantic-core version constraint from >=2.18.2,<2.44.0 to >=2.18.2,<3 in both pyproject.toml and requirements.txt
  • The <2.44.0 upper bound was auto-generated by the Fern SDK generator (fernapi/fern-python-sdk v5.3.3) in commit 7a070a7 and was not based on any actual API incompatibility
  • Users with pydantic>=2.13.3 (which requires pydantic-core==2.46.3) were unable to install SDK v1.11.0, forcing them to downgrade to v1.9.0

Root Cause

The SDK only uses three stable pydantic-core APIs:

  • PydanticUndefined (sentinel value comparison)
  • core_schema (schema building in Rfc2822DateTime)
  • to_jsonable_python (JSON serialization)

None of these APIs have changed across pydantic-core 2.x releases. The <2.44.0 cap was an artifact of the Fern code generator, not a deliberate compatibility boundary.

Changes

File Change
pyproject.toml pydantic-core = ">=2.18.2,<3"
requirements.txt pydantic-core>=2.18.2,<3
poetry.lock Regenerated (cosmetic metadata from Poetry 2.4.1)
tests/test_pydantic_core_compat.py 14 new tests verifying all pydantic-core usage patterns

Test plan

  • All 14 new pydantic-core compatibility tests pass, covering every pydantic_core import in the SDK
  • Full test suite passes (63 passed, 4 skipped for optional aiohttp)
  • mypy type checking passes (2069 source files, no issues)
  • ruff linting passes

Linear Issue

PRO-2816

Note for maintainers: The Fern SDK generator may re-introduce this constraint on the next regeneration. Consider adding pyproject.toml and requirements.txt to .fernignore, or configuring the Fern generator to not pin pydantic-core with a restrictive upper bound.

🤖 Generated with Claude Code

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
Vapi Tasker @claude
fix: relax pydantic-core upper bound from <2.44.0 to <3
1c08910 
The pydantic-core<2.44.0 constraint was auto-generated by the Fern SDK
generator (fernapi/fern-python-sdk v5.3.3) in commit 7a070a7 and was not
based on any actual incompatibility. The SDK only uses stable pydantic-core
APIs (PydanticUndefined, core_schema, to_jsonable_python) that have been
unchanged across all 2.x releases.

This constraint caused a dependency conflict for users with pydantic>=2.13.3,
which requires pydantic-core==2.46.3, forcing them to downgrade to SDK v1.9.0.

The new constraint >=2.18.2,<3 allows all pydantic-core 2.x versions while
guarding against a hypothetical 3.0 breaking change.

Resolves: PRO-2816

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@ghost ghost added the merge-queue label May 20, 2026
@dhruva-vapi
dhruva-vapi force-pushed the tasker/PRO-2816-fix-pydantic-core-version-conflict branch from b503747 to 1c08910 Compare June 4, 2026 03:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

merge-queue

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

0 participants

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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.