-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update pydantic to v2.7.3 #17781
Update pydantic to v2.7.3 #17781
Conversation
The changelog type |
1 similar comment
The changelog type |
The changelog type |
The |
The changelog type |
00f94ca
to
acdc9ef
Compare
The changelog type |
The |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Will be taken care with #17802 |
What does this PR do?
Motivation
Additional Notes
Pydantic v2.7.3 update is a breaking change for datadog_checks_base. This requires datamodel-code-generator to be updated which results in the auto generated model names to be updated for multiple of integrations, it basically pluralizes the model names, for example
Counter
becomesCounters
. So theddev validate models
will fail for this PR for all the affected integrations.The corrective path for that is to use the to be released datadog_checks_base version (mostly v37.0.0) and then run ddev validate models to fix the integrations. Apply those changes and release all the affected integrations.
This is a case of circular dependency, we are going to solve this by allowing the master pipeline to be in an unstable state (i.e., failing pipelines) for few hours till this is resolved.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged