@testspectra/cli 1.1.8-rc.24 → 1.1.8-rc.25

package/README.md

@@ -44,31 +44,34 @@ portable JS, so one npm package can't ship a single binary that works on every O
 `@testspectra/cli` follows the same pattern as esbuild/swc/turbo:
 
 - `@testspectra/cli` itself ships **no native binary** — only the JS launcher (`bin/spectra.js`).
-- The binary is published as four separate, platform-locked packages under `cli/npm/`:
+- The binary is published as three separate, platform-locked packages under `cli/npm/`:
   - `@testspectra/cli-darwin-arm64`
   - `@testspectra/cli-win32-x64`
-  - `@testspectra/cli-win32-arm64`
   - `@testspectra/cli-linux-x64`
 
+  (Windows arm64 has no native build — `resolveBinaryPath()` throws a clear "not supported"
+  error there instead of pointing at a package that was never published.)
+
   Each has `os`/`cpu` fields in its `package.json`, so npm/pnpm/yarn only ever download the one
   matching the installing machine.
-- `@testspectra/cli` lists all four as `optionalDependencies`, pinned to an exact version (not
+
+- `@testspectra/cli` lists all three as `optionalDependencies`, pinned to an exact version (not
   `^`) that always matches the `@testspectra/cli` release it ships with.
 - At runtime, `RustCoreBridge.resolveBinaryPath()` (`cli/src/runner/bridge.ts`) resolves the
   binary from whichever platform package got installed (`require.resolve('@testspectra/cli-<platform>/package.json')`),
   falling back to the monorepo's local build output (`core/target/release/...`) for local dev
   where no optional package is installed.
-- If a user's platform/arch isn't one of the four above, install succeeds (optional deps just
+- If a user's platform/arch isn't one of the three above, install succeeds (optional deps just
   get skipped) but `resolveBinaryPath()` throws a clear "not supported" error at run time.
 
 ### Building & releasing all platforms
 
-`scripts/build-cross-platform-binaries.js` builds the binary for all four platforms from a
+`scripts/build-cross-platform-binaries.js` builds the binary for all three platforms from a
 single macOS machine and copies each into `cli/npm/<platform>/bin/`:
 
 - **macOS arm64** — native `cargo build` (this machine only builds arm64; there's no x64 macOS
   package).
-- **Windows x64 / arm64** — cross-compiled via [`cargo-xwin`](https://github.com/rust-cross/cargo-xwin)
+- **Windows x64** — cross-compiled via [`cargo-xwin`](https://github.com/rust-cross/cargo-xwin)
   (`cargo install cargo-xwin`), which downloads the MSVC CRT/Windows SDK bits needed for linking.
   reqwest's default `native-tls` backend uses Schannel on Windows, so no OpenSSL cross-compile
   headaches here.
@@ -79,8 +82,8 @@ single macOS machine and copies each into `cli/npm/<platform>/bin/`:
   Docker must be running for this step.
 
 `scripts/release-cli-local.sh` runs this automatically, then stamps every `cli/npm/*/package.json`
-and `cli/package.json`'s `optionalDependencies` with the target version, packs all five tarballs,
-and (with `--publish`) publishes the four platform packages before `@testspectra/cli` itself.
+and `cli/package.json`'s `optionalDependencies` with the target version, packs all four tarballs,
+and (with `--publish`) publishes the three platform packages before `@testspectra/cli` itself.
 
 ---
 

package/bin/.testspectra-runner.hash

@@ -0,0 +1 @@
+2db95c618fc201b3c5e4b2f56e93c5e5fca36ba0d31250c65c98aabed5385361