Fix DagVersion when clearing tasks with run on latest version (#65835)

[Codingaditya17]

This backports the DagVersion alignment fix from #65835 to the 3.1 line.

When clearing task instances with run_on_latest_version=True, the cleared task instances should use the latest serialized DAG version. For queued or running DagRuns, the DagRun's created DAG version and bundle version also need to be aligned so the next task execution uses the latest DAG bundle instead of the older one.

This issue was reported against Airflow 3.1.6 in #67657. The fix already exists on newer branches, but was missing from v3-1-test.

Testing:

• uv run ruff check airflow-core/src/airflow/models/taskinstance.py

[Codingaditya17]

The failing checks appear unrelated to this backport.

This PR only changes airflow-core/src/airflow/models/taskinstance.py.

The current failures are in unrelated areas:

• OTEL integration tests under airflow-core/tests/integration/otel/test_otel.py
• Static check failure in providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py
• generate-openapi-spec modifying generated files

I verified the changed file locally with:

uv run ruff check airflow-core/src/airflow/models/taskinstance.py

and it passed.

[Codingaditya17]

The current failing static checks appear unrelated to this backport.

This PR only changes airflow-core/src/airflow/models/taskinstance.py.

The static check failure is from providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py, and the OpenAPI hook is generating a change in airflow-core/src/airflow/api_fastapi/core_api/openapi/_private_ui.yaml. Neither file is touched by this PR.

The integration failure is also in OTEL tests under airflow-core/tests/integration/otel/test_otel.py.

I verified the changed file locally with:

uv run ruff check airflow-core/src/airflow/models/taskinstance.py

and it passed.

[potiuk]

@Codingaditya17 A few things need addressing before review — see our Pull Request quality criteria.

• ❌ Pre-commit / static checks. See docs.
• ❌ Build docs. See docs.
• ❌ Other failing CI checks. See docs.

No rush.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

[Codingaditya17]

Addressed the static check failures.

Changes added:

• Fixed the edge3 ruff failure by avoiding the undefined workloads type reference in _process_workloads.
• Included the generated OpenAPI spec update from generate-openapi-spec.

Verified locally:

uv run ruff check providers/edge3/src/airflow/providers/edge3/executors/edge_executor.py airflow-core/src/airflow/models/taskinstance.py

git diff --check

[jscheffl]

Note that the v3-1-test branch is currently not maintained anymore, only very low probably a fix on v3-2-test might be cut, else from main we will start releasing 3.3.0 soon.

[Codingaditya17]

Thanks for the clarification.

Since v3-1-test is no longer maintained, I will stop chasing CI failures on this branch.

Given that this was reported against 3.1.6, would you prefer that I close this PR, or should I check whether a focused backport to v3-2-test is still useful?

[jscheffl]

As far as I see the original fix was backported in #66901 to v3-2-test maintenance branch and should have been released last week together with 3.2.2. So I assume nothing need to be done on-top. You can close the PR in my view.