Conversation
3090598 to
fbae196
Compare
fbae196 to
b449cdb
Compare
|
Closing since we're good with the pydantic bump. If we want to remove the bump, we can re-open and fix the aliasing as mentioned by kaxil. |
b449cdb to
77a789f
Compare
This reverts commit 9516a77.
6131186 to
d077ec2
Compare
Backport failed to create: v3-1-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 0e1832c v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
* Fix make_partial_model * Revert "Bump pydantic min version to 2.12.3 (apache#63570)" This reverts commit 9516a77. * Fix CI
* Fix make_partial_model * Revert "Bump pydantic min version to 2.12.3 (apache#63570)" This reverts commit 9516a77. * Fix CI
* Fix make_partial_model * Revert "Bump pydantic min version to 2.12.3 (apache#63570)" This reverts commit 9516a77. * Fix CI
* Fix make_partial_model * Revert "Bump pydantic min version to 2.12.3 (apache#63570)" This reverts commit 9516a77. * Fix CI
* Fix make_partial_model * Revert "Bump pydantic min version to 2.12.3 (apache#63570)" This reverts commit 9516a77. * Fix CI
Fixing implementation which was brittle and not working on pydantic 2.12.0
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.