c8ctl-plugin-nano 1.6.2 → 1.7.0

package/README.md

@@ -577,13 +577,18 @@ scope we own) so the names can never be squatted or npm-security-held:
 | `@nanobpm/c8ctl-plugin-nano-darwin-x64`    | darwin | x64   |
 | `@nanobpm/c8ctl-plugin-nano-linux-x64`     | linux  | x64   |
 | `@nanobpm/c8ctl-plugin-nano-linux-arm64`   | linux  | arm64 |
+| `@nanobpm/c8ctl-plugin-nano-linux-armv7`   | linux  | arm (v7) |
+| `@nanobpm/c8ctl-plugin-nano-linux-armv6`   | linux  | arm (v6) |
 | `@nanobpm/c8ctl-plugin-nano-win32-x64`     | win32  | x64   |
 
-The root `c8ctl-plugin-nano` lists all five as `optionalDependencies` (pinned to
-the exact release version, injected into the published tarball at release time).
-npm installs only the one matching the host, so each user downloads a single
-binary. The mapping lives in `platforms.mjs` — the single source of truth shared
-by the build/publish scripts and the plugin's runtime resolution.
+The root `c8ctl-plugin-nano` lists all of these as `optionalDependencies` (pinned
+to the exact release version, injected into the published tarball at release
+time). npm installs only those matching the host, so each user downloads a single
+binary — **except on 32-bit ARM**, where npm's `cpu` field is just `arm` for both
+armv6 and armv7, so both install and `platformForHost` picks the right one at
+runtime via the host's `arm_version` (falling back to the armv6 build, which also
+runs on armv7). The mapping lives in `platforms.mjs` — the single source of truth
+shared by the build/publish scripts and the plugin's runtime resolution.
 
 ### Binary delivery contract (upstream CI)
 
@@ -599,6 +604,8 @@ nanobpm-gateway-rest-server-darwin-arm64
 nanobpm-gateway-rest-server-darwin-x64
 nanobpm-gateway-rest-server-linux-x64
 nanobpm-gateway-rest-server-linux-arm64
+nanobpm-gateway-rest-server-linux-armv7
+nanobpm-gateway-rest-server-linux-armv6
 nanobpm-gateway-rest-server-win32-x64.exe
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "c8ctl-plugin-nano",
-  "version": "1.6.2",
+  "version": "1.7.0",
   "type": "module",
   "description": "c8ctl plugin to start, inspect, and stop a local Nano BPM (nanobpmn) cluster",
   "main": "c8ctl-plugin.js",
@@ -49,10 +49,12 @@
     "semantic-release": "^25.0.3"
   },
   "optionalDependencies": {
-    "@nanobpm/c8ctl-plugin-nano-darwin-arm64": "1.6.2",
-    "@nanobpm/c8ctl-plugin-nano-darwin-x64": "1.6.2",
-    "@nanobpm/c8ctl-plugin-nano-linux-x64": "1.6.2",
-    "@nanobpm/c8ctl-plugin-nano-linux-arm64": "1.6.2",
-    "@nanobpm/c8ctl-plugin-nano-win32-x64": "1.6.2"
+    "@nanobpm/c8ctl-plugin-nano-darwin-arm64": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-darwin-x64": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-linux-x64": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-linux-arm64": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-linux-armv7": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-linux-armv6": "1.7.0",
+    "@nanobpm/c8ctl-plugin-nano-win32-x64": "1.7.0"
   }
 }

package/platforms.mjs

@@ -7,6 +7,10 @@
  *            squatted or npm-security-held the way an unscoped name can.
  *   - os:    the npm "os" field value (process.platform)
  *   - cpu:   the npm "cpu" field value (process.arch)
+ *   - armVersion: (32-bit ARM only) the host ARM version this binary targets.
+ *            npm's `cpu` is just "arm" for BOTH armv6 and armv7, so the two
+ *            32-bit ARM packages share os/cpu and are disambiguated at runtime
+ *            by the host's reported ARM version (see `platformForHost`).
  *   - triple: the Rust target triple (informational; used by the Nano BPM CI)
  *   - asset: the GitHub Release asset name uploaded by the Nano BPM CI
  *   - bin:   the binary file name inside the platform package
@@ -52,6 +56,24 @@ export const PLATFORMS = [
     asset: `${BIN_BASENAME}-linux-arm64`,
     bin: BIN_BASENAME,
   },
+  {
+    pkg: '@nanobpm/c8ctl-plugin-nano-linux-armv7',
+    os: 'linux',
+    cpu: 'arm',
+    armVersion: 7,
+    triple: 'armv7-unknown-linux-gnueabihf',
+    asset: `${BIN_BASENAME}-linux-armv7`,
+    bin: BIN_BASENAME,
+  },
+  {
+    pkg: '@nanobpm/c8ctl-plugin-nano-linux-armv6',
+    os: 'linux',
+    cpu: 'arm',
+    armVersion: 6,
+    triple: 'arm-unknown-linux-gnueabihf',
+    asset: `${BIN_BASENAME}-linux-armv6`,
+    bin: BIN_BASENAME,
+  },
   {
     pkg: '@nanobpm/c8ctl-plugin-nano-win32-x64',
     os: 'win32',
@@ -62,7 +84,30 @@ export const PLATFORMS = [
   },
 ];
 
+/**
+ * The npm-reported ARM version of the host (6, 7, 8, ...), or 0 when unknown or
+ * not ARM. Node stamps this into `process.config` at build time: a 32-bit
+ * hardfloat build reports 6 (Pi 1 / Zero) or 7 (Pi 2/3/4 on a 32-bit OS, most
+ * modern 32-bit SBCs). Absent on 64-bit and non-ARM builds.
+ */
+function hostArmVersion() {
+  const v = parseInt(process.config?.variables?.arm_version, 10);
+  return Number.isFinite(v) ? v : 0;
+}
+
 /** The platform package that matches the host running this code, or undefined. */
 export function platformForHost(platform = process.platform, arch = process.arch) {
+  // 32-bit ARM: process.arch is 'arm' for BOTH armv6 and armv7, so os/cpu alone
+  // can't choose between the two packages. Pick on the host's ARM version. An
+  // armv6 binary also runs on armv7 (v7 is backward-compatible), so when the
+  // version is unknown fall back to armv6 — the universally-runnable 32-bit
+  // hardfloat build.
+  if (platform === 'linux' && arch === 'arm') {
+    const want = hostArmVersion() >= 7 ? 7 : 6;
+    return (
+      PLATFORMS.find((p) => p.os === 'linux' && p.cpu === 'arm' && p.armVersion === want) ||
+      PLATFORMS.find((p) => p.os === 'linux' && p.cpu === 'arm' && p.armVersion === 6)
+    );
+  }
   return PLATFORMS.find((p) => p.os === platform && p.cpu === arch);
 }