Awesome, it's great to see this becoming real.

Thank you to all of you who contributed to this,
Vikram

On Fri, Nov 13, 2026 at 4:58 AM Tzu-ping Chung via dev <
[email protected]> wrote:

> Dear Airflow community,
>
> I'm happy to announce that the Apache Airflow TypeScript SDK 1.0.0 was
> just released.
>
> With the TypeScript SDK you can define an entire Dag in TypeScript, with
> no Python file at all: the schedule, the tasks, their options, the
> dependencies between them, branching, task groups, human-in-the-loop tasks
> and triggering another Dag. You can also keep the Dag in Python and
> implement only its stub tasks in TypeScript. It runs on Airflow 3.4, and
> you will need Node 22 or later to build your Dags.
>
> The released sources can be downloaded via
> https://downloads.apache.org/airflow/ts-sdk/1.0.0/
>
> We also made this version available on npm for convenience:
> `npm install @apache-airflow/ts-sdk`
> https://www.npmjs.com/package/@apache-airflow/ts-sdk/v/1.0.0
> The earlier unscoped `apache-airflow-ts-sdk` package will not receive
> further releases.
>
> The TypeScript SDK guide is available at:
>
> https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/language-sdks/typescript.html
>
> The API reference is available at:
> https://airflow.apache.org/docs/ts-sdk/stable/
>
> If you encounter any issue or would like to provide feedback, please
> discuss in the `#sig-lang-sdks` Slack channel:
> https://apache-airflow.slack.com/archives/C08UCFRNAD8
>
> Many thanks to everyone who wrote or reviewed the TypeScript SDK changes
> that went into this release.
> Special thanks to two community contributors: Shivam Rastogi (@shivaam),
> who started the TypeScript SDK initiative during the Airflow 3.3.0
> timeline, and Guan-Ming Chiu (@guan404ming), who filled many of its feature
> gaps during the Airflow 3.4.0 timeline.
>
> Best regards,
> Jason & TP
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to