From 8e7f1a97ca2b8b294c10d004aa7a45035c8ba933 Mon Sep 17 00:00:00 2001 From: Kaxil Naik Date: Tue, 22 Apr 2025 18:48:50 +0530 Subject: [PATCH] Fix broken spell check ``` RELEASE_NOTES.rst:345: (im) Airflow 3 resolves im inconsistency by requiring File path: /opt/airflow/airflow-core/docs/RELEASE_NOTES.rst Incorrect Spelling: 'im' Line with Error: 'Airflow 3 resolves im inconsistency by requiring ' ==================================================================================================== If there are spelling errors related to class or function name, make sure those names are quoted with backticks '`' - this should exclude it from spellcheck process. If there are spelling errors in the summary above, and the spelling is correct, add the spelling to docs/spelling_wordlist.txt or use the spelling directive. Check https://sphinxcontrib-spelling.readthedocs.io/en/latest/customize.html#private-dictionaries for more details. If there are no spelling errors in the summary above, there might be an issue unrelated to spelling. Please review the traceback. ``` --- RELEASE_NOTES.rst | 2 +- reproducible_build.yaml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/RELEASE_NOTES.rst b/RELEASE_NOTES.rst index f5197b2973bdd..4df06ea010716 100644 --- a/RELEASE_NOTES.rst +++ b/RELEASE_NOTES.rst @@ -342,7 +342,7 @@ In Airflow 2, the ``xcom_pull()`` method allowed pulling XComs by key without sp DB model defines task_id as part of the XCom primary key. This created ambiguity: if two tasks pushed XComs with the same key, ``xcom_pull()`` would pull whichever one happened to be first, leading to unpredictable behavior. -Airflow 3 resolves im inconsistency by requiring ``task_ids`` when pulling by key. This change aligns with the task-scoped nature of +Airflow 3 resolves this inconsistency by requiring ``task_ids`` when pulling by key. This change aligns with the task-scoped nature of XComs as defined by the schema, ensuring predictable and consistent behavior. DAG Authors should update their dags to use ``task_ids`` if their dags used ``xcom_pull`` without ``task_ids`` such as:: diff --git a/reproducible_build.yaml b/reproducible_build.yaml index e8a278565cdba..c196df3876937 100644 --- a/reproducible_build.yaml +++ b/reproducible_build.yaml @@ -1,2 +1,2 @@ -release-notes-hash: 07533055cb46f0d05c39b200665aeb61 -source-date-epoch: 1745320897 +release-notes-hash: 77a6fba681cf21973ca9712136d1b51a +source-date-epoch: 1745327923