Shahar Epstein
f92281e1d0
* Drop Python 3.10 from CI, Breeze and the container images 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. * Explain when to drop a Python version from the CI version list The comment above ALL_PYTHON_MAJOR_MINOR_VERSIONS described only keeping dropped versions so cherry-picks to older branches stay tested. Python 3.10 is removed from the list because the 3.10 drop is also cherry-picked to v3-4-test, so no release branch that still receives cherry-picks from main supports 3.10. The comment now spells out both phases so the next version drop follows the same rule. The Docker image changelog gets its Python 3.10 entry under Airflow 3.4.0 here, next to the image change itself, as was done for Python 3.9.
NOTE! The files in this folder are generated by pre-commit based on airflow sources. They are not supposed to be manually modified.
You can read more about pre-commit hooks here.
-
provider_dependencies.json- is generated based onprovider.yamlfiles inairflow/providersand based on the imports in the provider code. If you want to add new dependency to a provider, you need to modify the correspondingprovider.yamlfile. This file is git-ignored (used to be committed) and it is generated automatically / dynamically when needed by either breeze or pre-commit hooks. -
provider_metadata.json- is generated based onprovider.yamlfiles, airflow constraints and tags for the providers. It contains historical metadata in providers that were released - it is useful to generate information in release notes and it is used to generate SBOM information for the providers. It is manually regenerated usingbreeze release-management generate-providers-metadatacommand." -
PYPI_README.md- is generated from the comprehensiveREADME.mdof the project, which contains exhaustive project details. Unlike the fullREADME.md,PYPI_README.mdis a distilled version tailored for PyPI, focusing on select sections. This subset is produced by thegenerate-pypi-readmepre-commit hook specified in the.pre-commit-config.yamlfile. This hook triggers automatically whenever the related sections in theREADME.mdchange, ensuring alignment between the two files. -
devel_deps.txtis a file containing development-only dependencies of Airflow. They were generated for Airflow 2.9.3 by running./dev/get_devel_deps.shscript. -
dep_tree.txtis a file containing the dependency tree of Airflow. It was generated for Airflow 2.9.3 by running this inside breeze:
uv tree --no-dedupe > /opt/airflow/generated/dep_tree.txt
dependency_depth.jsonis a fie containing the dependency depth of Airflow. It was generated for Airflow 2.9.3 by running this inside breeze:
cat /opt/airflow/generated/dep_tree.txt | python /opt/airflow/scripts/in_container/get_dependency_status.py >/opt/airflow/generated/dependency_depth.json