Skip to content

Upgrade ruff to latest version (0.12.1) #52562

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

Merged
merged 1 commit into from
Jun 30, 2025

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Jun 30, 2025

Fixes #52551


^ 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.

@boring-cyborg boring-cyborg bot added area:dev-tools area:task-sdk backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch labels Jun 30, 2025
@potiuk potiuk requested review from gopidesupavan and eladkal June 30, 2025 11:32
@potiuk potiuk force-pushed the upgrade-ruff-to-latest-version branch from 0eb9660 to 90d6f51 Compare June 30, 2025 15:06
@potiuk potiuk force-pushed the upgrade-ruff-to-latest-version branch 2 times, most recently from df91257 to 0c4f660 Compare June 30, 2025 17:17
@potiuk potiuk force-pushed the upgrade-ruff-to-latest-version branch from 0c4f660 to 2b68d07 Compare June 30, 2025 18:44
@potiuk potiuk merged commit 4b8cd25 into apache:main Jun 30, 2025
190 of 192 checks passed
@potiuk potiuk deleted the upgrade-ruff-to-latest-version branch June 30, 2025 21:23
Copy link

Backport failed to create: v3-0-test. View the failure log Run details

Status Branch Result
v3-0-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 4b8cd25 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-tools area:task-sdk backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ruff is held by apache-airflow
5 participants