This is an automated email from the ASF dual-hosted git repository.
potiuk 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 071bf3f4f3b Use EmailOperator from smtp provider (#49386)
071bf3f4f3b is described below
commit 071bf3f4f3bf1ec88b3d0b5140fe6e81e5edc79a
Author: Amogh Desai <amoghrajesh1...@gmail.com>
AuthorDate: Thu Apr 17 15:20:25 2025 +0530
Use EmailOperator from smtp provider (#49386)
---
airflow-core/docs/core-concepts/taskflow.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/airflow-core/docs/core-concepts/taskflow.rst
b/airflow-core/docs/core-concepts/taskflow.rst
index 73150735bd4..29e91eb4413 100644
--- a/airflow-core/docs/core-concepts/taskflow.rst
+++ b/airflow-core/docs/core-concepts/taskflow.rst
@@ -25,7 +25,7 @@ If you write most of your dags using plain Python code rather
than Operators, th
TaskFlow takes care of moving inputs and outputs between your Tasks using
XComs for you, as well as automatically calculating dependencies - when you
call a TaskFlow function in your DAG file, rather than executing it, you will
get an object representing the XCom for the result (an ``XComArg``), that you
can then use as inputs to downstream tasks or operators. For example::
from airflow.sdk import task
- from airflow.providers.email import EmailOperator
+ from airflow.providers.smtp.operators.smtp import EmailOperator
@task
def get_ip():
