@upfluxhq/cli 1.0.1 → 1.0.2

package/README.md

@@ -100,6 +100,8 @@ upflux release [options]
 | `-m, --mandatory` | | Mark update as mandatory |
 | `-r, --rollout <number>` | | Rollout percentage (0-100, default: 100) |
 | `-v, --version-range <range>` | | Binary version range (e.g., >=1.0.0) |
+| `--min-binary-version <version>` | | Minimum native binary version required. Devices below this are directed to update from the App Store / Play Store before receiving this OTA. |
+| `--skip-native-check` | | Skip automatic native change detection (useful in CI/CD) |
 | `--dev` | | Create development bundle |
 | `--skip-bundle` | | Skip bundling, use existing files in output dir |
 | `--schedule` | | Create as draft, set schedule time in dashboard |
@@ -168,6 +170,63 @@ upflux release --label v1.0.0 --capacitor --web-dir dist
 
 ---
 
+## Native Change Detection
+
+The CLI automatically detects native code changes since your last release and warns you when a store update may be required. This helps prevent devices from receiving OTA updates that depend on native features not yet available in their installed binary.
+
+### How It Works
+
+1. After each successful release, the CLI saves the current **git commit hash** to `.upflux`.
+2. On the next release, it runs `git diff <lastHash>..HEAD` against native files.
+3. If changes are found, it warns you and offers to auto-set `--min-binary-version`.
+
+> **Note:** Detection requires git. If the project is not a git repo, detection is silently skipped.
+
+### Files Watched
+
+| File | What is detected |
+|---|---|
+| `android/app/build.gradle` | `versionName` bump, `minSdkVersion` change |
+| `android/app/src/main/AndroidManifest.xml` | New permissions |
+| `ios/Podfile` | New native pods |
+| `ios/Podfile.lock` | Any pod version change |
+| `package.json` | New native dependency packages |
+
+### Example Interaction
+
+```
+⚠️  Native changes detected since last release:
+
+   Android:
+   • build.gradle: versionName → 2.0.0
+   • AndroidManifest.xml: New permission: android.permission.CAMERA
+
+   💡 Suggested flags:
+     --min-binary-version 2.0.0
+     --version-range ">=2.0.0"
+
+? How would you like to handle these native changes?
+❯ Auto-apply suggested flags (--min-binary-version 2.0.0 --version-range ">=2.0.0")
+  Enter min-binary-version manually
+  Continue without (not recommended for native changes)
+```
+
+### Setting `--min-binary-version` Manually
+
+```bash
+# Require devices to have at least v2.0.0 binary before receiving this OTA
+upflux release --label v2.0.0-ota --min-binary-version 2.0.0 --version-range ">=2.0.0"
+```
+
+### Skipping in CI/CD
+
+```bash
+# In CI, skip interactive detection and pass flag explicitly
+upflux release --label v2.0.0 --min-binary-version 2.0.0 --skip-native-check
+```
+
+---
+
 ### `status`
 
 Check deployment status and recent releases.
@@ -290,7 +349,9 @@ The CLI stores credentials in `.upflux` in the current directory:
       "deploymentName": "staging"
     }
   ],
-  "activeIndex": 0
+  "activeIndex": 0,
+  "lastReleaseHash": "a3f8c12d...",
+  "lastReleaseLabel": "v1.5.0"
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@upfluxhq/cli",
-    "version": "1.0.1",
+    "version": "1.0.2",
     "description": "Upflux CLI for managing OTA updates",
     "main": "dist/index.js",
     "types": "dist/index.d.ts",