I'm integrating Vapi into our Python codebase and ran into a dependency conflict with the latest vapi-server-sdk (1.11.0). The SDK pins pydantic-core=2.13.3, which requires pydantic-core==2.46.3. As a workaround, I've pinned to1.9.0, which doesn't have that constraint.   A couple of questions:   1. What's the reason behind the pydantic-core<2.44.0 cap? Is there a known incompatibility we should be aware of?   2. Are there plans to relax this constraint in upcoming releases?

This is very likely a hard pinning decision from Vapi to keep the SDK aligned with a specific tested "pydantic-core" range, not your environment being wrong. In most cases I’ve seen with similar Python SDKs, the "pydantic-core <2.44" cap is there because newer "pydantic-core" releases introduced subtle ABI/serialization changes that break SDK-generated models or async schema validation in edge cases. Right now, your workaround (pinning 1.9.0) is actually the expected safe path if your stack already depends on newer Pydantic 2.13+. On the roadmap side, this kind of constraint is usually relaxed once the SDK fully re-validates against latest Pydantic 2.x minor releases, so I’d expect it to move rather than stay long-term. If you want, I can help you isolate exactly which model/serialization path is triggering the conflict so you don’t have to stay pinned that low. @ManuPerte

So a new version without this pydantic-core constraint is expected right? Do you have any timeline for it? If so, we can wait.