pulse-updates 1.0.13 → 1.0.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pulse-updates",
-  "version": "1.0.13",
+  "version": "1.0.14",
   "description": "OTA updates for React Native - lightweight alternative to expo-updates",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",

package/scripts/publish.mjs

@@ -777,8 +777,9 @@ async function publish(options) {
   }
   logSuccess(`Created release: ${release.id}`);
 
-  // Crash-prediction preflight: warn (and abort unless --force) if this release references native
-  // modules that weren't in the previous good release for this runtime version.
+  // Crash-prediction preflight: REFUSE the publish (fail-closed) if this release references native
+  // modules that weren't in the previous good release for this runtime version — native code can't ship
+  // over the air, so it would crash the installed cohort. Override with --allow-native-change.
   let preflight = null;
   try {
     const pfRes = await fetch(`${config.apiUrl}/api/releases/${release.id}/preflight`, {
@@ -790,17 +791,24 @@ async function publish(options) {
   }
   if (preflight) {
     for (const w of preflight.warnings || []) log(`⚠  ${w}`);
-    // Only NEW NATIVE modules are risky for OTA (native code can't ship over the air); JS changes
-    // are always fine. Warn by default; only block when the publisher opts into --strict.
-    if (!preflight.ok) {
-      if (options.strict) {
+    // Only NEW NATIVE modules are risky for OTA (native code can't ship over the air); JS changes are
+    // always fine. FAIL-CLOSED by default: a new native module referenced by this JS bundle that isn't
+    // in the previous good build for this runtime-version would CRASH the whole installed cohort on load,
+    // so we refuse the publish. Override only with --allow-native-change (you certify the native module
+    // is already in the installed binary). `--no-native-check` skips the gate entirely.
+    if (!preflight.ok && !options['no-native-check']) {
+      const allow = options['allow-native-change'] || options.force;
+      if (!allow) {
         throw new Error(
-          'Aborting (--strict): this release references native modules new to it — they cannot ship ' +
-          'over the air. Ship them in a new native binary first.'
+          `Refusing to publish: this release references native module(s) NOT in the previous good build ` +
+          `for runtime-version ${config.runtimeVersion}/${config.platform}. Native code cannot ship over ` +
+          `the air — this OTA would crash the installed cohort on load. Ship a NEW native binary (and bump ` +
+          `the runtime-version) first. If you are certain the native module is already in the installed ` +
+          `binary, re-run with --allow-native-change.`
         );
       }
-      log('⚠  Continuing: native-module changes detected (above). Only matters if those native modules ' +
-        'are not already in the installed binary. Re-run with --strict to block on this.');
+      logWarning('--allow-native-change: publishing despite detected native-module changes. If those ' +
+        'native modules are NOT already in the installed binary, this OTA will crash the cohort.');
     }
   }
 
@@ -989,7 +997,11 @@ ${colors.cyan}Options:${colors.reset}
   --entry-file <file>     Entry file (default: index.ts)
   --skip-bundle           Skip bundle creation (use existing)
   --dry-run               Build + validate locally without creating a release on the server
-  --strict                Abort publish if new native modules are detected (default: warn only)
+  --allow-native-change   Publish even though new native modules were detected (you certify they're
+                          already in the installed binary). Default is FAIL-CLOSED: a new native module
+                          not in the shipped build is refused (it would crash the cohort over the air).
+  --no-native-check       Skip the native-mismatch gate entirely (not recommended)
+  --strict                (deprecated — blocking on native changes is now the default)
   --build <number>        Build number (shown in version, e.g., 1.0.0.42)
   --message <msg>         Release message/notes
   --key-id <id>           Key id for keygen (default: auto-generated)