Dev-iL opened a new pull request, #63596:
URL: https://github.com/apache/airflow/pull/63596
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
This change stops the migration test workflow from defaulting to Airflow
`2.11.0` and instead derives the minimum Airflow version from the Python
version used in CI.
### Why this is needed:
Today, DB migration tests effectively rely on a hardcoded default. That
becomes wrong as soon as a newer Python version is introduced that is not
supported by Airflow `2.11.0`. Without this
helper, we would need to keep adding special-case logic somewhere else to
say that DB tests must not use 2.11 constraints on Python 3.13 and newer.
We already know the minimum supported Airflow version for Python 3.13, so
there is no reason for Python 3.14 or later to fall back to an older and
unrelated default. A new Python version
should inherit the constraint from the previous known Python version until
a newer minimum is explicitly defined.
### What this gives us:
- Removes an irrelevant `2.11.0` fallback from migration tests.
- Makes new Python versions inherit the latest known minimum Airflow
version instead of silently using an incompatible one.
- Avoids scattering Python-version exceptions for DB tests in CI logic.
- Centralizes the compatibility mapping in a small helper with unit
coverage.
- Makes the migration workflow more maintainable as Python support evolves.
This keeps the migration test setup aligned with actual Airflow/Python
compatibility and prevents avoidable CI failures when new Python versions are
added.
---
##### 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: Codex GPT-5.4 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]
