-
Notifications
You must be signed in to change notification settings - Fork 15.3k
fix(ci): Bump uv versions #53228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ci): Bump uv versions #53228
Conversation
this change already merged right? |
I was thinking the same thing, that you updated these parts. However, some versions are still in the old version in main. For example, please see below. This is still in the old version. So I assumed it should show any changes in that case 🤔 Line 531 in da7073a
|
e3d650d
to
179c80e
Compare
It failed again on the main branch on the previous run too along with some python versions |
Yep. This time properly - it found Python needs to be upgraded. Previously it failed on rate limit and did not see that Old Python versions should be upgraded as well :). |
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 43d8c3b v3-0-test This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
I kept that separate to make it easy to review :) |
(cherry picked from commit 43d8c3b) Co-authored-by: Bugra Ozturk <[email protected]>
(cherry picked from commit 43d8c3b) Co-authored-by: Bugra Ozturk <[email protected]>
https://github.com/apache/airflow/actions/runs/16235766476/job/45845681492
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.