AlexWaygood opened a new pull request, #44287:
URL: https://github.com/apache/airflow/pull/44287

   [pypi.org/project/ruff/0.7.3](https://pypi.org/project/ruff/0.7.3/)
   
   Hi! I just released Ruff 0.8.0. This release removes a few rules that had 
been deprecated for a few releases, so Ruff 0.8.0 would have started emitting 
warnings when linting trio due to the fact that you have some of these 
now-removed rules explicitly ignored in your Ruff config.
   
   This PR gets rid of the removed rules from your Ruff config. There's also 
some additional changes made here; let me know if any of them are undesirable, 
and I can revert them:
   - The `flake8-type-checking` rules have been recoded from `TCH` to `TC`; I 
updated `noqa` comments and configuration settings related to these so that 
they use the new error codes
   - `dev/breeze/src/airflow_breeze/utils/console.py` was changed slightly due 
to autofix for UP015, which has been improved in the latest release
   
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   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 
[newsfragments](https://github.com/apache/airflow/tree/main/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]

Reply via email to