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

   - related: #71843
   
   ## Why
   
   `ts-sdk/README.md` is in `package.json` `files`, so it is the page rendered 
on https://www.npmjs.com/package/apache-airflow-ts-sdk. Its last ~160 lines are 
contributor and release-manager machinery, which is noise on a public package 
page.
   
   ## What
   
   - Move everything after the auto-generated compatibility matrix into a new 
`ts-sdk/DEVELOPMENT.md`
   - Add a `Links` section to `ts-sdk/README.md`
   - Make the remaining relative links absolute (`example/`, 
`capabilities.yaml`).
   - Fix release examples that used `ts-sdk/1.0.0-beta1` while `package.json` 
is `0.1.0-beta1`.
   - `ts-sdk/example/README.md`: coordinator key `"node"` -> `"ts"`, matching 
`ts-sdk/README.md` and `typescript.rst`.
   
   `DEVELOPMENT.md` is deliberately not in `files`. `REQUIRED_ROOT_FILES` in 
`ts-sdk/scripts/verify-package.mjs` allows only `LICENSE`, `NOTICE`, 
`README.md`, and `package.json` at the tarball root, so the published artifact 
is unchanged.
   
   ## Verification
   
   ```bash
   prek run --files ts-sdk/README.md ts-sdk/DEVELOPMENT.md 
ts-sdk/example/README.md ts-sdk/package.json
   prek run --hook-stage manual verify-ts-sdk-package --all-files
   ```
   
   ## Notes before cutting the release
   
   Not changed here:
   
   1. npm `latest` still points at the `0.0.1-beta1` name-reservation 
placeholder. Publishing `0.1.0-beta1` under `npm_tag=beta` leaves a bare `npm 
install apache-airflow-ts-sdk` installing the no-code placeholder.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes, with help of Claude Code 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]

Reply via email to