Conversation
shahar1
force-pushed
the
drop-py310/1-ci-breeze-docker
branch
from
October 3, 2026 13:07
2c24528 to
f1f9d33
Compare
shahar1
added this pull request to stack #74160
October 3, 2026 13:08
1 task done
shahar1
commented
Oct 3, 2026
shahar1
commented
Oct 3, 2026
shahar1
commented
Oct 3, 2026
shahar1
marked this pull request as ready for review
October 3, 2026 13:40
shahar1
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
henry3260,
jason810496,
jedcunningham,
jscheffl and
potiuk
as code owners
October 3, 2026 13:40
This was referenced Oct 3, 2026
1 task done
shahar1
force-pushed
the
drop-py310/1-ci-breeze-docker
branch
2 times, most recently
from
October 4, 2026 06:41
0528099 to
0965104
Compare
1 task done
shahar1
force-pushed
the
drop-py310/1-ci-breeze-docker
branch
from
October 4, 2026 17:53
0965104 to
edfd62b
Compare
… verify CI Temporary: drops out on rebase once #74200 is merged.
Python 3.10 reaches end of life in October 2026 and more and more of Airflow's dependencies have already dropped it, which makes the 3.10 leg the slowest and most fragile part of CI. This is the first layer of the stack that moves the baseline to Python 3.11: Breeze stops offering 3.10, the default Python for CI, Breeze and the images moves to 3.11, and the PGP path for verifying the Python tarball goes away because every remaining version ships Sigstore bundles. Python 3.10 stays in the historical version lists that Breeze uses to reason about older Airflow releases, and in the CI image restore action that release branches still rely on. The distributions still declare Python 3.10 in this layer; layer 7 bumps them once the code no longer carries 3.10-only constructs. Until then the provider metadata generator keeps its own 3.10-inclusive version list, and the prek minimum-Python check keeps 3.10 because its script header still pins it to a 3.10 interpreter until layer 2. The shared-distribution and scripts test jobs run uv without an interpreter pin, so uv picks the runner's system Python, which is 3.10 on the current images. Pinning them to the default CI Python keeps them on a supported interpreter regardless of the runner image. The image build speed check builds the CI image from the registry cache within a fixed budget. A PR that changes install_os_dependencies.sh or the embedded GPG keys misses the cache for the layer that compiles Python from source. That compile took about 4.5 minutes for Python 3.10 but 11 to 18 minutes for 3.11 and newer on hosted runners, so the budget is raised to fit a cold Python 3.11+ build.
potiuk
force-pushed
the
drop-py310/1-ci-breeze-docker
branch
from
October 4, 2026 23:43
edfd62b to
1cd3fc1
Compare
This branch has not been deployed
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.
Python 3.10 reached EOL on Oct. 1, 2026, and according to Apache Airflow policy we should drop its support as well. This PR removes 3.10 from the CI matrix, Breeze, and the Docker images, changing the min. version to 3.11.
related: #74148
AI Summary
Python 3.10 reaches end of life in October 2026 and a growing number of dependencies have already dropped it. This layer removes 3.10 from the CI matrix, Breeze and the images, and moves the default Python to 3.11.ALLOWED_PYTHON_MAJOR_MINOR_VERSIONS/ALL_PYTHON_MAJOR_MINOR_VERSIONSare3.11–3.14, providers compatibility matrix runs on 3.11, deadPYTHON_TO_MIN_AIRFLOW_MAPPING+ unusedis_airflow_version_supported_for_pythonremoved. Breeze command output docs regenerated (the ~100 SVG/TXT files are hook output).3.11in composite actions and workflows; the--no-explain-whyworkaround for 3.10 infinalize-tests.ymlgoes away.AIRFLOW_PYTHON_VERSIONis 3.11; the PGP branch for verifying the Python tarball is removed (3.11+ publish Sigstore bundles),python-3.10.ascand its key entry go with it.scripts/, test constants and prek utility messages;get_min_airflow_version_for_pythonkeyed from 3.11.update-tested-versionshook; newsfragment added.Deliberately kept:
.github/actions/prepare_all_ci_imagesstill restores 3.9/3.10 images (shared with release branches, #45268);ALL_HISTORICAL_PYTHON_VERSIONS,PYTHON_3_10_TO_3_14,ALL_PYTHON_VERSION_TO_PATCHLEVEL_VERSION["3.10"]stay for older Airflow releases.Distributions still declare Python 3.10 in this layer; layer 7 bumps them once the code carries no 3.10-only constructs.
Layer 1 of 9 of the Python 3.10 drop (supersedes #74144, which carried the whole change in one PR). Each layer is meant to be green on its own: the script metadata bump comes first because prek picks the hook interpreter from it, and the ruff fixes land before the
requires-pythonbump because ruff infers its target per distribution from the nearestpyproject.toml.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5.1) following the guidelines