* ci: split Aliyun OSS sync into a separate post-release workflow
The OSS upload and verification steps were adding significant time to the
release workflow's critical path. Move them into a new `sync-release-to-oss.yml`
workflow that triggers on `release: published`, running asynchronously after
the release completes.
Key changes:
- Extract all OSS steps (ossutil install, credential config, asset upload,
verification, hosted installation sync, latest VERSION pointer) into
`sync-release-to-oss.yml`
- Switch `gh release create` to use CI_BOT_PAT so the release event can
trigger the new downstream workflow (GITHUB_TOKEN events don't trigger
other workflows)
- Add `workflow_dispatch` input for manual re-runs on failure
- New workflow downloads release assets from GitHub Release instead of
rebuilding them
This decouples publishing from CDN distribution: the release finishes as
soon as npm publish + GitHub Release are done, and China CDN sync happens
in parallel without blocking.
* fix(test): update install-script test to check sync-release-to-oss.yml
The test asserts OSS sync steps exist in the workflow. Now that these
steps live in sync-release-to-oss.yml instead of release.yml, update the
test to read from the correct file and add assertions that release.yml
no longer contains OSS logic.
* fix(ci): address review feedback for OSS sync split
- Add 'Verify Standalone Archives' step before gh release create in
release.yml as a pre-publish safety gate (wenshao)
- Add concurrency group to sync-release-to-oss.yml to prevent race
conditions when multiple releases publish close together (wenshao)
- Update test to assert verify step exists in release.yml
* chore: add comment explaining CI_BOT_PAT requirement [skip ci]