Update dependencies, fix pydantic-core usage, fix CI issues#7150
Merged
Update dependencies, fix pydantic-core usage, fix CI issues#7150
Conversation
Deploying with
|
| Latest commit: |
1aa2d46
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1575e8df.pydantic-docs2.pages.dev |
| Branch Preview URL: | https://use-pydantic-core-2-6-0.pydantic-docs2.pages.dev |
Contributor
Author
|
please review |
adriangb
approved these changes
Aug 16, 2023
davidhewitt
approved these changes
Aug 16, 2023
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
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.
make refresh-lockfiles). This includedpyrightandruff, which resulted in needing to change some stuff for type-checking/linting.strthat were equal were actually the same object in memory, which clearly isn't guaranteed. It wasn't unreasonable to want them to be the same, because they were previously both the exact str instanceFooEnum.FOO.value, but anyway I don't think it should be required and I changed the test to just check the types were exactly the same and the values were equal).Selected Reviewer: @lig