aviralgarg05 opened a new pull request, #63030: URL: https://github.com/apache/airflow/pull/63030
### What this PR does This PR improves the usability of cross-DAG XCom pulls for workflows that trigger downstream DAG runs. The issue asks for a clear way to pull XCom from a specific triggered DAG run (identified by `trigger_run_id`). Airflow already supports `run_id` in `xcom_pull`, but this was not clearly documented in the core XCom docs and did not have targeted runtime coverage for this exact usage pattern. This change addresses that by: 1. Adding a focused Task SDK regression test that validates `xcom_pull(..., dag_id=..., run_id=...)` is propagated correctly. 2. Updating XCom documentation with an explicit example showing how to use `trigger_run_id` from `TriggerDagRunOperator` to read values from the triggered DAG run. This keeps behavior intact while making the feature discoverable and preventing regressions. related: #62988 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (Codex) Generated with help of Codex following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --- ### Tests run - `pytest task-sdk/tests/task_sdk/execution_time/test_task_runner.py -k "xcom_pull_with_explicit_dag_id_and_run_id or xcom_pull_with_include_prior_dates"` (run multiple times) - `ruff check task-sdk/tests/task_sdk/execution_time/test_task_runner.py` ### Files changed - `task-sdk/tests/task_sdk/execution_time/test_task_runner.py` - `airflow-core/docs/core-concepts/xcoms.rst` -- 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]
