Pydantic Validation has come a long way since the V2 release in June 2023. Fourteen minor releases later (the most recent being V2.14), V2 is faster, more correct, and supports far more of the Python type system than it did at launch.
Usage has grown with it. Pydantic is now one of the 20 most downloaded packages on PyPI, at more than 800 million downloads a month.
We are starting work on the next major release, Pydantic V3. Here is what to expect, and what it means for V1 and V2.
Pydantic V3: 🙂 not 😱
We know the V1 to V2 migration was painful for some of you. That is why we have kept V1 maintained for the past three years.
V3 will be different. As described in the tracking issue, every breaking change will be one of:
- a correctness fix, such as a bug that affects a minority of users (for example, #9992).
- a change where you can easily opt back in to the previous behavior.
V1 deprecations and the pydantic.v1 namespace will also be removed.
There will be no API overhaul on the scale of the V1 to V2 migration.
Over time, we have collected a long list of issues that can only be fixed in a major release. We won't tackle every one of them, but we want to get as many as possible into V3.
There is no release date yet, but we are aiming to have V3 close to its final state by the end of the year.
Pydantic V1
We have released Pydantic V1.10.27, the final V1 release. This release fixes some security issues, described in the changelog.
The same fixes are included in the pydantic.v1 namespace shipped with Pydantic V2.14.2.
Pydantic V2
Once V3 is out, V2 will keep receiving fixes for major bugs and security issues. How long that lasts depends on how smoothly the migration to V3 goes, so we aren't setting an end date yet. We won't drop V2 until we are confident most users have moved to V3.
Enterprise support
Pydantic itself stays open source. Its license, releases, documentation, and issue tracker remain open to everyone.
Some teams need more than that. You might still run V1 in production and can't migrate yet, or you might want help planning the move to V3. For those cases, we offer enterprise support: direct access to Pydantic engineers, 24/7 priority support, and an SLA matched to how you operate. Your agreement defines the release lines we cover and how we coordinate with you when a vulnerability affects one of them.
Contact us to discuss what your team needs.
Have questions or feedback on the roadmap? Join the conversation on our community Slack or open a discussion on GitHub.
