potiuk opened a new pull request, #61598: URL: https://github.com/apache/airflow/pull/61598
This commit synchronizes CI/CD infrastructure and development tooling from the main branch to the 2.11 release branch, including: GitHub Actions workflows: - Pin GitHub actions to specific commit SHAs for security (actions/[email protected]) - Remove unnecessary 'secrets: inherit' declarations from workflow calls - Add 'id-token: write' permission for prod image builds - Update generate-constraints workflow with PyPI constraints support - Remove unneeded 'recheck-old-bug-report' workflow Breeze development tool updates: - Upgrade Python minimum version from 3.9 to 3.10 - Update dependencies: black (>=25.0.0), packaging (>=25.0), pytest (>=8.3.3) - Add 'prek' and 'restructuredtext-lint' dependencies - Pin rich-click <1.9.0 to avoid breaking changes - Unpin flit and flit-core versions for flexibility - Update flit build-system requirement to >=3.11 Docker and CI infrastructure: - Update Dockerfile base images and entrypoint scripts - Refresh pre-commit hook configurations - Update Breeze documentation and generated CLI output images Code improvements: - Add selective check for migration SQL files - Update path utilities and test fixtures - Refresh uv.lock with updated dependency resolution The main point behind upgrading Python version to 3.10 is that Python 3.9 is officially end-of-life and many of the depenedencies had already stopped releasing even security fixes for 3.9. Since the upcoming 2.11.1 version is mainly a security-focused release, we decided to drop support for Python 3.9 in order to be able to upgrade all related dependencies to latest security patch versions. There are absolutely minimal changes in behaviour between Python 3.9 and 3.10 and we have not experienced virtually any problems because of this - other than dependency issues, so it should be very minimal overhead for anyone to upgrade to Python 3.10 even if they used Python 3.9. <!-- 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 --> --- ##### 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". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] 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` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). -- 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]
