Dev-iL opened a new pull request, #63592:
URL: https://github.com/apache/airflow/pull/63592
<!-- 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 makes the new-Python-version bootstrap flow explicit and safer.
When a new Python version is added, the first constraints generation run has
no previous constraints file to diff against on `constraints-main`. This PR
adds an opt-in bootstrap path for that case in `run_generate_constraints.py`:
when `--allow-missing-previous-constraints-file` is set, a `404` for the
previous constraints file is treated as expected, logged clearly, and the diff
is skipped. Other HTTP and request failures still fail normally.
The same opt-in is wired through `breeze release-management
generate-constraints`, and the Docker/common constraints download fallback is
narrowed so it only falls back to an empty constraints file for the explicit
bootstrap case instead of masking any missing constraints URL. This keeps
regular builds strict while still allowing the initial constraints file for a
newly supported Python version to be created.
These new code paths should be used rarely, roughly once a year when adding
support for a new Python version.
Tests:
- `uv run --project dev/breeze pytest tests/test_shell_params.py
tests/test_release_management_commands.py -xvs`
- `bash -n scripts/docker/common.sh`
- `git diff --check`
The script-level constraints bootstrap test was added, and the remaining
end-to-end verification is expected to come from CI.
---
##### 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]
