Skip to content

Bump pydantic min version to 2.12.3#63570

Merged
gopidesupavan merged 1 commit intoapache:mainfrom
gopidesupavan:bump-pydantics-min
Mar 14, 2026
Merged

Bump pydantic min version to 2.12.3#63570
gopidesupavan merged 1 commit intoapache:mainfrom
gopidesupavan:bump-pydantics-min

Conversation

@gopidesupavan
Copy link
Member

@gopidesupavan gopidesupavan commented Mar 13, 2026

CI started failing in the lowest-deps tests: https://github.com/apache/airflow/actions/runs/23058551095/job/66982917534?pr=63531#step:8:2304.

It looks like lowest-deps is resolving pydantic to 2.12.0, which is causing the failures. after testing in local with 2.12.3 its working fine for this version. looking at the changelog https://docs.pydantic.dev/latest/changelog/#v2123-2025-10-17 thats potential fix? didnt deep dive.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {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.

@gopidesupavan gopidesupavan merged commit 9516a77 into apache:main Mar 14, 2026
106 checks passed
@gopidesupavan gopidesupavan deleted the bump-pydantics-min branch March 14, 2026 03:39
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 9516a77 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools area:providers area:registry area:task-sdk backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch kind:documentation provider:edge Edge Executor / Worker (AIP-69) / edge3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants