@bugsee/cli 0.7.6 → 0.7.7

package/README.md

@@ -12,7 +12,7 @@ npx bugsee-cli --version
 
 ## How the binary gets here
 
-The binary is **not** in this package. It ships in five per-platform packages,
+The binary is **not** in this package. It ships in six per-platform packages,
 declared as `optionalDependencies`:
 
 | Package                    | `os` / `cpu`       |
@@ -22,6 +22,7 @@ declared as `optionalDependencies`:
 | `@bugsee/cli-linux-arm64`  | `linux` / `arm64`  |
 | `@bugsee/cli-linux-x64`    | `linux` / `x64`    |
 | `@bugsee/cli-win32-x64`    | `win32` / `x64`    |
+| `@bugsee/cli-win32-arm64`  | `win32` / `arm64`  |
 
 npm installs only the one matching your machine and skips the rest. Nothing is
 downloaded at install time, so this works with `--ignore-scripts`, with a

package/lib/index.js

@@ -29,7 +29,7 @@ function vendorPath(triple) {
  *
  *  1. The platform package installed as an optionalDependency. This is the
  *     normal path and the whole point of the package split: npm picks exactly
- *     one of the five by `os`/`cpu`, and it works under `--ignore-scripts`
+ *     one of the six by `os`/`cpu`, and it works under `--ignore-scripts`
  *     because nothing had to run to put the binary there.
  *  2. `vendor/`, where the postinstall fallback downloads to when (1) is
  *     unavailable — `--no-optional`, a registry mirror that carries only the

package/lib/platforms.js

@@ -17,14 +17,14 @@
 // release.yml. Check the plan with `dist plan --output-format=json` — see the
 // `allow-dirty` comment in Cargo.toml.)
 //
-// NO Windows arm64 (`aarch64-pc-windows-msvc` / @bugsee/cli-win32-arm64) — see
-// bugsee/bugsee-cli#20. It is one row here plus one triple in `targets`, but it
-// cannot be validated before a tag push: ci.yml has no target matrix and
-// `pr-run-mode = "plan"`, while dist's `host` job needs EVERY
-// build-local-artifacts leg to succeed. A failing leg therefore means no
-// GitHub Release at all — and so no S3 mirror and no npm publish, since both
-// chain off `workflow_run.conclusion == 'success'`. Adding it speculatively
-// would risk the whole release pipeline, npm packaging included.
+// Windows arm64 (`aarch64-pc-windows-msvc`) IS published as of 0.7.7 — see
+// bugsee/bugsee-cli#20 for why it was absent before. It cross-compiles under
+// cargo-xwin only if `ring` can assemble its ARM64 Windows `.S` files, which it
+// cannot, so that leg builds NATIVELY on a `windows-11-arm` runner instead
+// (`[workspace.metadata.dist.github-custom-runners]` in Cargo.toml). ci.yml
+// build-checks the target on every PR so the leg cannot break a tag release:
+// dist's `host` job needs EVERY build-local-artifacts leg, and a failing leg
+// means no GitHub Release, hence no S3 mirror and no npm publish.
 
 "use strict";
 
@@ -76,6 +76,14 @@ const PLATFORMS = Object.freeze({
     archiveExt: ".zip",
     label: "Windows x86_64",
   },
+  "aarch64-pc-windows-msvc": {
+    pkg: "@bugsee/cli-win32-arm64",
+    os: "win32",
+    cpu: "arm64",
+    bin: "bugsee-cli.exe",
+    archiveExt: ".zip",
+    label: "Windows arm64",
+  },
 });
 
 /** Release-asset filename cargo-dist publishes for a triple. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bugsee/cli",
-  "version": "0.7.6",
+  "version": "0.7.7",
   "description": "Bugsee CLI — cross-platform symbol collection, conversion, and upload.",
   "keywords": [
     "bugsee",
@@ -34,10 +34,11 @@
     "node": ">=14.18"
   },
   "optionalDependencies": {
-    "@bugsee/cli-darwin-arm64": "0.7.6",
-    "@bugsee/cli-darwin-x64": "0.7.6",
-    "@bugsee/cli-linux-arm64": "0.7.6",
-    "@bugsee/cli-linux-x64": "0.7.6",
-    "@bugsee/cli-win32-x64": "0.7.6"
+    "@bugsee/cli-darwin-arm64": "0.7.7",
+    "@bugsee/cli-darwin-x64": "0.7.7",
+    "@bugsee/cli-linux-arm64": "0.7.7",
+    "@bugsee/cli-linux-x64": "0.7.7",
+    "@bugsee/cli-win32-arm64": "0.7.7",
+    "@bugsee/cli-win32-x64": "0.7.7"
   }
 }

package/scripts/postinstall.js

@@ -7,7 +7,7 @@
 //   - `npm install --no-optional` / `--omit=optional` (and the CI images that
 //     bake that in), where npm never even looks at the platform packages;
 //   - an internal registry mirror or proxy that carries @bugsee/cli but not
-//     the five @bugsee/cli-<platform> scopes, where npm silently skips the
+//     the six @bugsee/cli-<platform> scopes, where npm silently skips the
 //     optional dependency and leaves nothing behind;
 //   - a platform we publish no package for at all.
 //