bbovenzi opened a new pull request, #75260: URL: https://github.com/apache/airflow/pull/75260
Backport of #74773 to `v3-4-test`, so 3.4.0 ships loop iterations numbered from one. Task loops are new in 3.4 and have not shipped in a release, so no stored run and no client depends on the old zero-based numbering. Leaving `v3-4-test` on zero would release the confusing numbering that #74773 removes, and force a breaking change later. **Merge after #74773 lands on main.** The cherry-pick trailer is intentionally omitted: the squash-merge commit does not exist yet, and a trailer naming the branch commit would be a dead reference in the permanent history. It can be added when #74773 merges. ### Differences from the commit on main One hunk was dropped. `airflow-core/tests/unit/api_fastapi/execution_api/versions/head/test_xcoms.py` on main contains `test_parsing_attempt_id_does_not_select_a_loop_iteration`, which comes from an unrelated PR that is not on `v3-4-test`. The two `steps[0]` → `steps[1]` edits inside it are therefore absent here. Nothing else differs: the changed-file set is identical, and a diff of the two commits' diffs shows only those two lines. ### Verification * All six generators re-run on this branch with zero drift — `generate-openapi-spec`, `generate-supervisor-schemas-snapshot`, `generate-tasksdk-datamodels`, `generate-airflowctl-datamodels`, `sync-ts-sdk-schemas`, `sync-go-sdk-schemas` — confirming the vendored artifacts match what `v3-4-test` produces rather than what main produces. * `validate_loop_decision` applies cleanly to the `stop: bool | None` signature already on `v3-4-test`. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) Claude Opus 5 Generated-by: Claude Opus 5 following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
