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

kaxil 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 dd9ad598d4b Fix broken class xrefs in standard provider docs (#73360)
dd9ad598d4b is described below

commit dd9ad598d4b379b420efac3a6d9930fb31b2f116
Author: Kaxil Naik <[email protected]>
AuthorDate: Sat Sep 19 03:36:24 2026 +0100

    Fix broken class xrefs in standard provider docs (#73360)
    
    DayOfWeekSensor's xref in the standard provider's sensor guide pointed at
    the pre-provider-split airflow.sensors.weekday path, which no longer
    exists; the class now lives under 
airflow.providers.standard.sensors.weekday.
    
    BaseXCom's xref in the common.io XCom backend guide pointed at
    airflow.models.xcom.BaseXCom, a deprecated compat shim. The task-sdk docs
    only expose it at the flat airflow.sdk.BaseXCom path (autoapiclass in
    task-sdk/docs/api.rst, autoapi_generate_api_docs=False elsewhere), matching
    the existing convention for this class of xref (e.g. 
airflow.sdk.ResumableJobMixin).
    
    The TimeSensor xref in the same sensor guide is also broken (points at a
    non-existent sensors.time_sensor module) but is left alone here since 
#69610,
    #69746, and #69925 are all open against that same paragraph.
---
 providers/common/io/docs/xcom_backend.rst    | 2 +-
 providers/standard/docs/sensors/datetime.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/providers/common/io/docs/xcom_backend.rst 
b/providers/common/io/docs/xcom_backend.rst
index 47c1bd8a869..0a5442f4d71 100644
--- a/providers/common/io/docs/xcom_backend.rst
+++ b/providers/common/io/docs/xcom_backend.rst
@@ -18,7 +18,7 @@
 Object Storage XCom Backend
 ===========================
 
-The default XCom backend is the :class:`~airflow.models.xcom.BaseXCom` class, 
which stores XComs in the Airflow database. This is fine for small values, but 
can be problematic for large values, or for large numbers of XComs.
+The default XCom backend is the :class:`~airflow.sdk.BaseXCom` class, which 
stores XComs in the Airflow database. This is fine for small values, but can be 
problematic for large values, or for large numbers of XComs.
 
 To enable storing XComs in an object store, you can set the ``xcom_backend`` 
configuration option to 
``airflow.providers.common.io.xcom.backend.XComObjectStorageBackend``. You will 
also need to set ``xcom_objectstorage_path`` to the desired location. The 
connection
 id is obtained from the user part of the url that you will provide, e.g. 
``xcom_objectstorage_path = s3://conn_id@mybucket/key``. Furthermore, 
``xcom_objectstorage_threshold`` is required
diff --git a/providers/standard/docs/sensors/datetime.rst 
b/providers/standard/docs/sensors/datetime.rst
index 2a45ecb6bd8..3633fa01e7b 100644
--- a/providers/standard/docs/sensors/datetime.rst
+++ b/providers/standard/docs/sensors/datetime.rst
@@ -55,7 +55,7 @@ Time will be evaluated against ``data_interval_end`` if 
present for the Dag run,
 DayOfWeekSensor
 ===============
 
-Use the :class:`~airflow.sensors.weekday.DayOfWeekSensor` to sense for day of 
week.
+Use the :class:`~airflow.providers.standard.sensors.weekday.DayOfWeekSensor` 
to sense for day of week.
 
 .. exampleinclude:: 
/../src/airflow/providers/standard/example_dags/example_sensors.py
     :language: python

Reply via email to