This is an automated email from the ASF dual-hosted git repository.

eladkal pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 64e4c065bf3 Fix minor display issue with migration to airflow 3 docs 
(#60749)
64e4c065bf3 is described below

commit 64e4c065bf317181e95d241b252eaceb68284eed
Author: Elad Kalif <[email protected]>
AuthorDate: Sun Jan 18 17:45:06 2026 +0200

    Fix minor display issue with migration to airflow 3 docs (#60749)
---
 airflow-core/docs/installation/upgrading_to_airflow3.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/airflow-core/docs/installation/upgrading_to_airflow3.rst 
b/airflow-core/docs/installation/upgrading_to_airflow3.rst
index e88ef8b0ad9..2e17cf621f7 100644
--- a/airflow-core/docs/installation/upgrading_to_airflow3.rst
+++ b/airflow-core/docs/installation/upgrading_to_airflow3.rst
@@ -118,7 +118,8 @@ To trigger these fixes, run the following command:
 
 .. note::
 
-    In AIR rules, unsafe fixes involve changing import paths while keeping the 
name of the imported member the same. For instance, changing the import from 
``from airflow.sensors.base_sensor_operator import BaseSensorOperator`` to 
``from airflow.sdk.bases.sensor import BaseSensorOperator`` requires ruff to 
remove the original import before adding the new one. In contrast, safe fixes 
include changes to both the member name and the import path, such as changing 
``from airflow.datasets impo [...]
+    In AIR rules, unsafe fixes involve changing import paths while keeping the 
name of the imported member the same. For instance, changing the import from 
``from airflow.sensors.base_sensor_operator import BaseSensorOperator`` to 
``from airflow.sdk.bases.sensor import BaseSensorOperator`` requires ruff to 
remove the original import before adding the new one. In contrast, safe fixes 
include changes to both the member name and the import path, such as changing 
``from airflow.datasets impo [...]
+    These adjustments do not require ruff to remove the old import. To remove 
unused legacy imports, it is necessary to enable the ``unused-import`` rule 
(F401) <https://docs.astral.sh/ruff/rules/unused-import/#unused-import-f401>`_
 
 You can also configure these flags through configuration files. See 
`Configuring Ruff <https://docs.astral.sh/ruff/configuration/>`_ for details.
 

Reply via email to