INTEG-2943 - pydantic v2 #157
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tora-kozic
reviewed
Aug 7, 2025
jdullum
approved these changes
Aug 11, 2025
Contributor
|
For the changelog, I would mention that this version will now require pydantic v2 with a short phrase about how users may or may not see impacts, along with a link to pydantics migration docs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Details of the pydantic v1->v2 migration here: https://docs.pydantic.dev/dev/migration/
None of our changes should directly impact customers, but changes to the underlying pydantic APIs may impact (for example if anyone was using something like
model.parse_raw()or something like that. Those methods are deprecated but should still work, but we should instead use the pydantic v2model.model_validate()or similar.