release-sdklisted

# Release Plugin SDK Trigger `wibus-wee/cradle-app`'s `release-plugin-sdk.yml` workflow and monitor it until `@cradleapp/plugin-sdk` is published to npm. ## Prerequisites Before the first CI release, configure npm **Trusted publishing** on `@cradleapp/plugin-sdk`: - Provider: GitHub Actions - Repository: `wibus-wee/cradle-app` - Workflow filename: `release-plugin-sdk.yml` If trusted publishing is not configured, CI publish will fail with authentication errors. ## Usage ```bash /release-sdk dev # Dev channel: sdk-dev-YYYYMMDD.N → npm tag dev /release-sdk 0.2.0 # Release channel: sdk-v0.2.0 → npm tag latest ``` ## Rules - Release tags live in this repository (`wibus-wee/cradle-app`). Tag the commit you want to publish (usually `origin/main`). - SDK tags use the `sdk-` prefix and are independent from desktop `v*` / `dev-*` tags. - Leave unrelated local files alone. - Use Cradle awaits for workflow completion; do not watch the run with a long polling loop. - Use only short bounded retries to let GitHub materialize run/check IDs. ## Version Logic - `dev` creates `sdk-dev-YYYYMMDD.N`. - Use remote tags, not npm versions, to find the next increment. - Example: `sdk-dev-20260707.1`, then `sdk-dev-20260707.2`. - CI publishes npm version `0.0.0-dev.<run_number>` with dist-tag `dev`. - A release version creates `sdk-vX.Y.Z`. - Accept `0.2.0` or `v0.2.0`; normalize to `sdk-v0.2.0`. - CI publishes that SemVer with dist-tag `latest`. ## Implementation