1.0.0-beta1 is already published as apache-airflow-ts-sdk and its
ts-sdk/1.0.0-beta1 tag is taken, so the first release under the
@apache-airflow/ts-sdk name needs a version of its own.
* Rename TypeScript SDK npm package to @apache-airflow/ts-sdk
* Take the TypeScript SDK release tarball name from npm pack
Building the tarball name by hand duplicates npm's naming rules for scoped
packages and can silently drift from what npm actually writes, so the
release job now uses the filename npm reports.
The example project is not published, so its name does not need to follow
the scoped package rename.
---------
* Allow TypeScript SDK releases from core release branches
The release workflow required the tagged commit to be an ancestor of main.
Cherry-picks onto a core release branch get new SHAs, so a release cut from
vX-Y-test or vX-Y-stable was rejected, which is where an SDK release is cut
once a core minor has branched.
* Match only real release branch names in the release check
A `v*-test` glob also accepts names like `vx-test`, which are not release
branches.
---------
* TS SDK: Bump to 1.0.0-beta1 and align README with the guide
Move the human-in-the-loop docs into the TypeScript SDK guide, describe the
TaskClient methods in a table, and trim the README and the API reference
landing page to a quick start that links to the guide.
* Keep the HITL params warning in the TypeScript SDK guide
---------
Jason(Zhe-You) Liu