Hi @potiuk @kaxil. I might need your help on yandex backward compat tests.

Previously, when we called persist, the function call chain was persist() -> BaseOperator.push_xcom() -> TI.push_xcom(). A redundant arg (execution_date) was added during the BashOperator Xcom push.

However, in our current persist(), we push Xcoms directly through a task instance without adding execution_date. This means the rewrite will change how persist() behaves in AF2 and its outputs will no longer match the expected output of the original test cases.

Given this, should I just modify the AF2 test cases, or is there a better way to handle this? Thanks.

Look at similar tests in google. I just fixed them a day ago or so: #52398 -> generally when in doubt - look for similar patterms in other providers.

One pre-commit is failing:

Update providers build files................................................Failed
- hook id: update-providers-build-files
- files were modified by this hook


--
diff --git a/providers/yandex/pyproject.toml b/providers/yandex/pyproject.toml
index 1eb44bd..876f8ad 100644
--- a/providers/yandex/pyproject.toml
+++ b/providers/yandex/pyproject.toml
@@ -73,7 +73,6 @@ dev = [
     "apache-airflow",
     "apache-airflow-task-sdk",
     "apache-airflow-devel-common",
-    "apache-airflow-providers-common-compat",
     # Additional devel dependencies (do not remove this line and add extra development dependencies)
     "responses>=0.25.0",
 ]

Yep. No more common.compat dependency - should be removed :)

Thanks @potiuk @kaxil for your help and review on this PR.