Andrushika opened a new pull request, #75054:
URL: https://github.com/apache/airflow/pull/75054
## Why
The Dag processor runs the bundle of a native TypeScript Dag again on every
re-parse, and the worker runs the same bundle for each task. So a bundle can
build its Dags from a file in the Dag bundle, and changing only that file
changes the live Dags with no rebuild. #74636 and #74710 test this end to end
for Go and Java, but nothing tests it for TypeScript yet.
## What
- `dynamic.ts` in `ts-sdk/example` makes one Dag per entry of the
`dags.yaml` next to the bundle, and `main.ts` registers them on the existing
bundle. `airflow-ts-pack` runs the bundle at pack time and fails when it serves
nothing, so a separate entry would need a `dags.yaml` shipped next to `dist/`.
- `test_ts_sdk_dynamic_dag.py` runs the same 3 → 5 → 2 Dag swap as the Go
and Java tests with the shared helper, and `ts.yml` copies the re-parse
settings of `go.yml`.
- The YAML parser is `js-yaml`, already in the lockfile. I first tried
`yaml`, but its Node build is CommonJS and calls `require("process")`, which
fails inside the ESM bundle.
related: #74636, #74710
---
##### Was generative AI tooling used to co-author this PR?
- [x] Yes (please specify the tool below)
Generated-by: Claude Code (Claude Opus 5.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]
