shahar1 opened a new pull request, #76076:
URL: https://github.com/apache/airflow/pull/76076

   Backport of #63733 to `airflow-ctl/v0-1-test` (cherry picked from 
ed51aff0562556fa1dd7d1ff6152018e70db03c2, path-limited).
   
   Airflow 3.3+ servers create runs with `run_type: operator_triggered` (from 
TriggerDagRunOperator). airflowctl 0.1.x's `DagRunType` lacks the value, so 
`dagrun list/get`, `dags trigger` and `dags list/get` fail validation on those 
runs. This adds the enum value; nothing changes for 3.2.x servers, which never 
send it.
   
   Left out: the execution API route change and its test (airflow-core does not 
ship from this branch).
   
   Checks: `pytest airflow-ctl/tests` 386 passed (the one failure, 
`test_server_connection_refused`, also fails on the unchanged branch locally); 
new airflowctl test fails without the change; 
`airflow-core/tests/unit/api/common/test_trigger_dag.py` 3 passed; UI `tsc 
--noEmit` clean.
   
   Generated files were regenerated on this branch rather than copied from 
`main` (codegen versions differ): the v2 spec, `_private_ui.yaml` and the 
simple-auth spec via `scripts/in_container/run_generate_openapi_spec.py` on 
Python 3.12, the airflowctl and task-sdk datamodels via the branch's `codegen` 
group, and the UI `openapi-gen` via `pnpm codegen`. On the unchanged branch 
these reproduce the committed files byte for byte. CI on this branch only runs 
the airflow-ctl tests, so please re-run the generators when reviewing.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5.5)
   
   Generated-by: Claude Code (Opus 5.5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to