@radhya/mach 2.0.42 → 2.0.43

package/docs/ota.md

@@ -22,7 +22,7 @@ mach ota setup
 mach ota verify
 ```
 
-Setup reads project ID, framework, channel, runtime policy, and existing URL from `mach.config.json`. Command flags have higher precedence. Interactive setup asks before installing dependencies; use `mach --yes ota setup` in automation. Use `--skip-install` only when dependencies are managed separately.
+Setup reads project ID, framework, channel, runtime policy, and existing URL from `mach.config.json`. Command flags have higher precedence. It also refreshes an older project-local `@radhya/mach` package so Expo prebuild uses a plugin compatible with the running CLI. Interactive setup asks before installing dependencies; use `mach --yes ota setup` in automation. Use `--skip-install` only when dependencies are managed separately.
 
 For a bare React Native project, setup may make these intentional changes:
 
@@ -54,7 +54,9 @@ The default `ON_LOAD` behavior downloads a compatible release on one cold launch
 
 ## Runtime compatibility
 
-The native binary and OTA manifest must contain the same runtime version. Mach injects the resolved runtime into Expo config during builds and publishes, and synchronizes it into committed bare native projects before a Mach build.
+The native binary and OTA manifest must contain the same runtime version. Mach injects the resolved runtime into Expo config during builds and publishes, and synchronizes it into committed bare native projects before a Mach build. Runtime precedence is command `--runtime-version`, `ota.runtimeVersion`, `ota.runtimeVersionPolicy`, Expo config, then package version fallback. When Mach has a policy, old hardcoded Expo runtime values do not override it.
+
+`mach ota verify`, `mach ota publish`, and OTA-enabled Expo builds validate the final resolved Expo URL, channel, and runtime. They stop with a repair instruction if the project-local plugin would embed different values.
 
 The default `appVersion` policy uses the app/package version as the compatibility boundary. Use an explicit `ota.runtimeVersion` or `--runtime-version` only when deliberately managing compatibility yourself.
 

package/expo-plugin/index.js

@@ -123,7 +123,7 @@ module.exports = function withMachDeepLinks(config) {
     }
     if (ota.runtimeVersion) {
       config.runtimeVersion = ota.runtimeVersion
-    } else if (!config.runtimeVersion && ota.runtimeVersionPolicy) {
+    } else if (ota.runtimeVersionPolicy) {
       config.runtimeVersion = { policy: ota.runtimeVersionPolicy }
     }
     config.extra.mach = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radhya/mach",
-  "version": "2.0.42",
+  "version": "2.0.43",
   "description": "Mach CLI: Cloud Build Orchestrator for React Native & Expo",
   "main": "dist/index.js",
   "type": "module",
@@ -16,6 +16,7 @@
   ],
   "scripts": {
     "build": "tsup src/index.ts src/commands/isolated-upload.ts --format esm --clean --minify --dts",
+    "test": "tsx --test src/**/*.test.ts && node --test tests/*.test.cjs",
     "start": "node dist/index.js",
     "dev": "tsx src/index.ts",
     "release": "semantic-release"