Dev-iL opened a new pull request, #74557:
URL: https://github.com/apache/airflow/pull/74557

   > [!IMPORTANT]
   > **Note to reviewers**: this is a manual stacked PR. Please review only the 
latest commit.
   
   Stack:
   1. https://github.com/apache/airflow/pull/74556
   2. https://github.com/apache/airflow/pull/74557 **(current PR)**
   
   related: 
   - #74555
   - #74408
   
   Python 3.15 is now an allowed CI image interpreter. The breeze CI image for 
3.15 could not be built from the existing metadata. Providers whose 
dependencies have no 3.15 wheels, such as 
`apache-airflow-providers-apache-kafka` (`confluent-kafka` builds from source), 
would fail the image build. The workspace packages also declared 
`requires-python` without 3.15, so the resolver rejected the interpreter.
   
   This PR:
   - Adds 3.15 to `ALLOWED_PYTHON_MAJOR_MINOR_VERSIONS` and 
`ALL_PYTHON_MAJOR_MINOR_VERSIONS` in 
`dev/breeze/src/airflow_breeze/global_constants.py`, and maps 3.15 to 3.15.0.
   - Raises `requires-python` for the root and the core distributions from 
`!=3.15` to `!=3.16`.
   - Adds `excluded-python-versions: "3.15"` to 42 providers' `provider.yaml`. 
The workspace root and the matching provider dependency declarations get 
`python_version != "3.15"` markers. Cassandra also keeps its 3.14 exclusion.
   - Splits the `moto[cloudformation]` extra in 
`providers/amazon/pyproject.toml` for 3.15, because cfn-lint declares `Python 
<3.15` on PyPI.
   - Adds `pyarrow` and `numpy` overrides to the root `pyproject.toml`. They 
keep the `apache-beam` caps (`pyarrow<26`, `numpy<2.5`) for the other 
interpreters and lift them for 3.15 (`pyarrow>=26`, `numpy>=2.5.2`). It also 
adds a `lazy-object-proxy<1.12` constraint for 3.15.
   - Adds dated `exclude-newer-package` exemptions for the first releases with 
3.15 wheels that fall inside the four-day cooldown: pydantic 2.14.0 and 
pydantic-core 2.50.0, httptools 0.9.0, aiohttp 3.14.5, and pyarrow 26.0.0. Each 
has a comment naming the release and the date to remove it.
   - Adds the 3.15 release-manager identity (`[email protected]`, issuer 
`https://github.com/login/oauth`, PEP 790) to the sigstore check in 
`scripts/docker/install_os_dependencies.sh`.
   - Makes `scripts/ci/prek/update_airflow_pyproject_toml.py` apply the 
exclusion marker to providers without a minimum version.
   - Includes the files the prek hooks regenerated from these changes: 
`uv.lock`, the Dockerfiles, provider `README.rst` files, the breeze help output 
and the PyPI README.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [x] Yes (please specify the tool below)
   
   Generated-by: Claude & Codex following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to