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

   ## Why
   
   The `@apache-airflow` npm scope is now available, so the TypeScript SDK 
should be published as `@apache-airflow/ts-sdk` instead of 
`apache-airflow-ts-sdk`.
   
   ```bash
   npm install @apache-airflow/ts-sdk
   ```
   
   ```ts
   import { Bundle, Dag } from "@apache-airflow/ts-sdk";
   import { approval } from "@apache-airflow/ts-sdk/hitl";
   ```
   
   ## What
   
   - Rename the package in `package.json` and add `publishConfig.access: 
"public"`, which a scoped package needs on its first publish.
   - Derive the release tarball name the way `npm pack` does for a scoped name 
(`apache-airflow-ts-sdk-<version>.tgz`).
   - Update the release workflow's package identity check and the `npm trust` / 
`npm stage` commands in `DEVELOPMENT.md`.
   - Update imports, path aliases, error messages, docs, ADRs, examples, tests 
and lockfiles. Rename the private example package to `ts-sdk-example`.
   
   The SDK is still in beta, so there is no compatibility shim for the old 
name. It will be deprecated on npm.
   
   One-time npm steps after merge:
   
   ```bash
   npm trust github @apache-airflow/ts-sdk --repo apache/airflow --file 
ts-sdk-release.yml \
     --environment ts-sdk-npm-release --allow-stage-publish --allow-publish
   # after the first release under the new name
   npm dist-tag add @apache-airflow/ts-sdk@<version> latest
   npm deprecate @apache-airflow/[email protected] "Placeholder, use a released 
version"
   npm deprecate apache-airflow-ts-sdk "Moved to @apache-airflow/ts-sdk"
   ```
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes, with help of 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)
   


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