Re: [I] Add ruff rules to catch deprecated Airflow imports for Airflow 3.1 [airflow]

["florian-meyrueis-al (via GitHub)" <gi...@apache.org>]

florian-meyrueis-al commented on issue #54714:
URL: https://github.com/apache/airflow/issues/54714#issuecomment-3858765005

   Hello, i hope i'm not coming too late to talk a bit about the ruff rules for migration to airflow3.
   
   We have discovered that some removal/replacement in airflow3 are not detected and fixed by ruff AIR3 rules.
   
   These are : 
   
   - usage of parameter "provide_context" in PythonOperator.
   This was deprecated in airflow2 and has been removed in Airflow3 . context is now always provided in PythonOperator
   So any dag using this should be modified accordingly.
   
   
   - In BaseOperator, usage of parameter trigger_rule="none_failed_or_skipped" has been replaced by "none_failed_min_one_success".
   Any Dag using an operator with this parameter must be updated with the correct value
   
   - apply_default decorator is now automatically deployed so it must removed of any dags.
   
   
   I wish i could do it myself, but i have no skill in rust.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org