@upfluxhq/cli 1.1.0 → 1.3.0

package/README.md

@@ -10,35 +10,61 @@ npm install -g @upfluxhq/cli
 pnpm add -g @upfluxhq/cli
 ```
 
+---
+
 ## Quick Start
 
 ```bash
-# 1. Authenticate with your publish keys (supports multiple!)
-upflux login --key <staging-publish-key>
-upflux login --key <production-publish-key>
+# 1. Initialize project config (creates upflux.json)
+upflux init
+
+# 2. Authenticate with your publish key (from Upflux dashboard)
+upflux login --key <publish-key>
 
-# 2. Upload a release (will prompt if multiple deployments)
-upflux release --label v1.0.0 --mandatory
+# 3. Publish a release (auto-increments buildNumber)
+upflux release
 
-# 3. Check release status
+# 4. Check deployment status
 upflux status
 ```
 
+---
+
 ## Commands
 
-### `login`
+### `init`
 
-Authenticate with the Upflux server. **Supports multiple credentials** - each login adds a new deployment.
+Interactive wizard to configure `upflux.json` in your project root. Replaces manual configuration in your app code with declarative deployment profiles.
 
 ```bash
-upflux login --key <publishKey>
+upflux init [options]
 ```
 
 | Option | Description |
 |--------|-------------|
-| `-k, --key <publishKey>` | Publish key for authentication |
+| `--force` | Overwrite existing `upflux.json` without prompting |
+
+**What it sets up:**
+- App ID & server URL
+- Initial `buildNumber` (`0`) and `runtimeVersion` (e.g. `1.0.0`)
+- Deployment profiles (`development`, `production`, etc.) with client keys (`upx_cli_*`)
+- Safe to commit to git — client keys are read-only
+
+---
+
+### `login`
+
+Authenticate with the Upflux server using your publish key. **Supports multiple credentials** — each login registers another deployment target.
 
-**Example output with multiple logins:**
+```bash
+upflux login --key <publishKey>
+```
+
+| Option | Required | Description |
+|--------|----------|-------------|
+| `-k, --key <publishKey>` | ✓ | Publish key (`upx_pub_*`) from the dashboard |
+
+**Example output with multiple credentials:**
 ```
 🔐 Verifying with server...
 ✓ Login successful!
@@ -54,7 +80,7 @@ upflux login --key <publishKey>
 
 ### `logout`
 
-Remove stored credentials.
+Remove stored publish credentials.
 
 ```bash
 upflux logout [options]
@@ -62,14 +88,14 @@ upflux logout [options]
 
 | Option | Description |
 |--------|-------------|
-| `--all` | Remove all credentials |
+| `--all` | Remove all stored credentials |
 
 **Example:**
 ```bash
-# Interactive selection to remove one
+# Interactive selection:
 upflux logout
 
-# Remove all credentials
+# Clear all credentials:
 upflux logout --all
 ```
 
@@ -77,159 +103,105 @@ upflux logout --all
 
 ### `release`
 
-Bundle and upload a new release. **Prompts to select deployment** if multiple are stored.
+Bundle and upload a new OTA release. Prompts for target deployment if multiple are configured.
 
 Automatically detects project type:
-- **React Native**: Uses `react-native bundle` command
-- **Capacitor**: Zips the web directory (detected via `capacitor.config.*`)
+- **React Native**: Runs `react-native bundle` for iOS and Android
+- **Capacitor**: Archives the web assets folder (detected from `capacitor.config.*`)
 
 ```bash
 upflux release [options]
 ```
 
-| Option | Required | Description |
-|--------|----------|-------------|
-| `-l, --label <label>` | ✓ | Release label (e.g., v1.0.0) |
-| `--platform <platform>` | | Target platform: `all`, `ios`, or `android` (defaults to `all`) |
-| `-a, --app <appId>` | | Application ID (auto-detected from credentials) |
-| `-d, --deployment <deploymentId>` | | Deployment ID (prompts if multiple) |
-| `-e, --entry-file <path>` | | Entry file for bundler (default: `index.js`) |
-| `-o, --output-dir <path>` | | Output directory for bundle (default: `./dist`) |
-| `-b, --bundle <path>` | | Skip bundling, use existing bundle file |
-| `--assets <paths...>` | | Skip auto-detection, use these asset files |
-| `-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 |
-| `--capacitor` | | Force Capacitor mode (auto-detected if capacitor.config exists) |
-| `--web-dir <path>` | | Web directory to bundle for Capacitor (default: from config or www) |
-
-**Examples:**
+| Option | Description |
+|--------|-------------|
+| `-l, --label <label>` | Release label (e.g. `v1.0.0`). **Optional** — if omitted, auto-increments `buildNumber` in `upflux.json` (e.g. `1.0.0+1`) |
+| `--platform <platform>` | Target platform: `all`, `ios`, or `android` (default: `all`) |
+| `-a, --app <appId>` | Application ID (auto-detected from stored credentials) |
+| `-d, --deployment <deploymentId>` | Target deployment ID (prompts if multiple exist) |
+| `-m, --mandatory` | Mark update as mandatory |
+| `-r, --rollout <number>` | Rollout percentage: `0`–`100` (default: `100`) |
+| `-v, --version-range <range>` | Target binary version semver range (e.g. `>=1.0.0`) |
+| `--min-binary-version <version>` | Minimum native binary version required. Devices below this receive store update prompts. |
+| `--skip-native-check` | Skip automatic git native change inspection |
+| `--schedule` | Create release as a draft to schedule release time via dashboard |
+| `-e, --entry-file <path>` | React Native entry file (default: `index.js`) |
+| `-o, --output-dir <path>` | Output directory for bundles (default: `./dist`) |
+| `-b, --bundle <path>` | Skip bundler, upload prebuilt bundle file |
+| `--assets <paths...>` | Explicit asset files or directories to include |
+| `--dev` | Create development bundle |
+| `--skip-bundle` | Skip bundling, reuse existing files in output directory |
+| `--capacitor` | Force Capacitor bundling mode |
+| `--web-dir <path>` | Custom web asset directory for Capacitor (default: from config or `www`) |
+
+#### Examples
 
 ```bash
-# Release to selected deployment (prompts if multiple)
-upflux release --label v1.2.0
+# Recommended: Auto-increment buildNumber from upflux.json (e.g. 1.0.0+1 -> 1.0.0+2)
+upflux release
 
-# iOS-only hotfix
-upflux release --label v1.2.1-ios-fix --platform ios
-
-# Android-only release with 50% rollout
-upflux release --label v1.2.2 --platform android --rollout 50
+# Release with explicit custom label
+upflux release --label v1.2.0
 
-# Mandatory update for all platforms
-upflux release --label v1.3.0 --mandatory
+# Mandatory release with gradual 25% rollout
+upflux release --mandatory --rollout 25
 
-# Schedule release (draft mode)
-upflux release --label v1.4.0 --schedule
+# iOS-only emergency hotfix
+upflux release --platform ios
 
-# Capacitor project with custom web directory
-upflux release --label v1.0.0 --capacitor --web-dir dist
-```
-
-**Example output:**
-```
-📦 Bundling for iOS...
-  ✓ iOS bundle created
-📦 Bundling for Android...
-  ✓ Android bundle created
-
-⬆ Uploading release...
-  App: app-970384d3
-  Deployment: 6933e683aa32fe18a1311bbb
-  Deployment Name: production
-  Label: v1.2.0
-  Platform: all
-  Bundle: ./dist/ios/index.ios.bundle
-  Assets: 24 file(s)
-  Rollout: 100%
-  Mandatory: No
-
-📋 Step 1/3: Requesting upload URLs...
-   ✓ Got 26 presigned URLs
-📤 Step 2/3: Uploading files directly to storage...
-   [1/26] index.ios.bundle
-   ...
-   ✓ Uploaded 26 files
-✅ Step 3/3: Confirming release...
-
-✓ Release uploaded successfully!
-──────────────────────────────────
-  ID: 693507a19f6d6a79267633e8
-  Label: v1.2.0
-  iOS Bundle: uploaded
-  Android Bundle: uploaded
-  Rollout: 100%
-  Mandatory: No
-  Status: active
-──────────────────────────────────
+# Capacitor release with custom build folder
+upflux release --capacitor --web-dir build
 ```
 
 ---
 
-## 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
+## Auto-incrementing Build Numbers
 
-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`.
+When releasing without `--label`, the CLI reads `upflux.json` at your project root:
 
-> **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
+1. Reads `runtimeVersion` (e.g., `"1.0.0"`) and current `buildNumber` (e.g., `0`)
+2. Increments `buildNumber` by 1 (`1`)
+3. Generates release label: `1.0.0+1`
+4. Writes updated `buildNumber` back to `upflux.json`
+5. Embeds updated `upflux.json` into the native assets directory
 
+```json
+{
+  "version": 1,
+  "app": {
+    "id": "app-970384d3",
+    "buildNumber": 1,
+    "runtimeVersion": "1.0.0"
+  },
+  "deployments": { ... }
+}
 ```
-⚠️  Native changes detected since last release:
 
-   Android:
-   • build.gradle: versionName → 2.0.0
-   • AndroidManifest.xml: New permission: android.permission.CAMERA
+> 💡 **Best Practice:** Commit `upflux.json` to git after running `upflux release` so the build counter is synchronized across your team and CI/CD pipelines.
 
-   💡 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)
-```
+## Native Change Detection
 
-### Setting `--min-binary-version` Manually
+The CLI automatically inspects native changes since your last release to prevent pushing OTA updates that depend on unreleased native code.
 
-```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"
-```
+### Files Monitored
 
-### Skipping in CI/CD
+| File | Monitored Changes |
+|---|---|
+| `android/app/build.gradle` | `versionName` changes, `minSdkVersion` bumps |
+| `android/app/src/main/AndroidManifest.xml` | Added/removed Android permissions |
+| `ios/Podfile` | Added native CocoaPods |
+| `ios/Podfile.lock` | Updated CocoaPod versions |
+| `package.json` | Newly added native dependencies |
 
-```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
-```
+If changes are detected, the CLI prompts you to automatically set `--min-binary-version`. In CI/CD environments, use `--skip-native-check` or specify `--min-binary-version` directly.
 
 ---
 
 ### `status`
 
-Check deployment status and recent releases.
+View deployment status, active release, rollout percentage, and recent releases.
 
 ```bash
 upflux status [options]
@@ -237,34 +209,26 @@ upflux status [options]
 
 | Option | Description |
 |--------|-------------|
-| `-n, --limit <number>` | Number of releases to show (default: 5) |
+| `-n, --limit <number>` | Number of recent releases to display (default: 5) |
 
-**Example output:**
+**Example:**
 ```
 ⚡ Fetching deployment status...
 
 ╭────────────────────────────────────────────────╮
 │  📱 app-970384d3 → production                  │
 │  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  │
-│  Current Release: v1.2.0 (iOS & Android)       │
+│  Current Release: 1.0.0+4 (iOS & Android)      │
 │  Status: ● active • 100% rollout               │
-│  Published: 2h ago                             │
+│  Published: 15m ago                            │
 ╰────────────────────────────────────────────────╯
-
-📦 Recent Releases (15 total)
-
-  Label        Platform  Status      Rollout   Published
-  ────────────────────────────────────────────────────────
-  v1.2.0       all       ● active    100%      2h ago
-  v1.1.0       all       ○ expired   100%      3d ago
-  v1.0.0       ios       ○ expired   100%      1w ago
 ```
 
 ---
 
 ### `generate-manifest`
 
-Fetch and display the manifest for a specific release.
+Fetch and display or export the update manifest for a specific release ID.
 
 ```bash
 upflux generate-manifest [options]
@@ -273,51 +237,7 @@ upflux generate-manifest [options]
 | Option | Required | Description |
 |--------|----------|-------------|
 | `-r, --release-id <id>` | ✓ | Release ID (MongoDB ObjectId) |
-| `-o, --output <path>` | | Save manifest to file |
-
-**Example:**
-```bash
-# Print manifest to stdout
-upflux generate-manifest --release-id 693507a19f6d6a79267633e8
-
-# Save to file
-upflux generate-manifest --release-id 693507a19f6d6a79267633e8 --output manifest.json
-```
-
----
-
-## Scheduled Releases
-
-Schedule releases to go live at a specific date and time. Perfect for coordinating updates with marketing campaigns, feature launches, or maintenance windows.
-
-### How It Works
-
-1. Create a release with the `--schedule` flag
-2. The release is uploaded as a **Draft**
-3. Set the scheduled time in the Upflux Dashboard
-4. The release automatically goes live at the scheduled time
-
-### Creating a Scheduled Release
-
-```bash
-# Create a draft release for scheduling
-upflux release --label v2.0.0 --schedule
-
-# Output:
-# ✓ Release uploaded successfully!
-#   ...
-#   Status: DRAFT
-#   📅 Set schedule time in dashboard
-```
-
-### Use Cases
-
-- **Feature launches** - Coordinate with marketing announcements
-- **Global releases** - Release at optimal times for different regions
-- **Maintenance windows** - Deploy during low-traffic periods
-- **Campaign coordination** - Sync with promotional events
-
-> 💡 **Tip:** Combine scheduled releases with rollout percentages for safer deployments. For example, schedule a 10% rollout first, then manually increase after monitoring.
+| `-o, --output <path>` | | Save manifest JSON to file |
 
 ---
 
@@ -327,67 +247,16 @@ upflux release --label v2.0.0 --schedule
 
 | Variable | Description | Default |
 |----------|-------------|---------|
-| `UPFLUX_API_URL` | API server URL | `https://api.upflux.in/api` |
-
-### Auth File
-
-The CLI stores credentials in `.upflux` in the current directory:
-
-```json
-{
-  "credentials": [
-    {
-      "key": "upflux_pub_xxx...",
-      "appId": "app-970384d3",
-      "deploymentId": "6933e683aa32fe18a1311bbb",
-      "deploymentName": "production"
-    },
-    {
-      "key": "upflux_pub_yyy...",
-      "appId": "app-970384d3",
-      "deploymentId": "6933e683aa32fe18a1311ccc",
-      "deploymentName": "staging"
-    }
-  ],
-  "activeIndex": 0,
-  "lastReleaseHash": "a3f8c12d...",
-  "lastReleaseLabel": "v1.5.0"
-}
-```
-
-> ⚠️ **Important:** Never commit the `.upflux` file to version control. It contains your publish keys. Add it to your `.gitignore`.
+| `UPFLUX_API_URL` | Upflux API server URL | `https://api.upflux.in/api` |
 
----
-
-## Publish Keys
-
-Publish keys are used to authenticate the CLI and can be found in the Upflux dashboard under **Settings → Keys**.
+### Auth Storage (`.upflux`)
 
-Key format: `upflux_pub_<prefix>_<secret>`
+Stored credentials and release metadata are saved in `.upflux` in the current project directory.
 
-Example: `upflux_pub_prod_a1b2c3d4e5f6...`
+> ⚠️ **Important:** Add `.upflux` to your `.gitignore`. It contains your publish keys (`upx_pub_*`).
 
 ---
 
-## Development
-
-```bash
-# Install dependencies
-pnpm install
-
-# Build
-pnpm run build
-
-# Run locally
-node dist/index.js --help
-```
-
-## Requirements
-
-- Node.js >= 18.0.0
-- For React Native projects: `react-native` CLI installed
-- For Capacitor projects: Built web assets in configured `webDir`
-
 ## License
 
 MIT

package/dist/client/apiClient.js

@@ -11,7 +11,6 @@ const configStore_1 = require("../config/configStore");
  */
 // const DEFAULT_BASE_URL = "http://localhost:3000/api";
 const DEFAULT_BASE_URL = "https://api.upflux.in/api";
-console.log(process.env.UPFLUX_API_URL || DEFAULT_BASE_URL);
 exports.apiClient = axios_1.default.create({
     baseURL: process.env.UPFLUX_API_URL || DEFAULT_BASE_URL,
 });

package/dist/client/directUpload.js

@@ -96,6 +96,16 @@ async function uploadFilesWithPresignedUrls(files, urls, options) {
             }
         }
         urlMap.set(relativePath, url);
+        // Also index by key after release path (releases/{appId}/{deploymentName}/{releaseLabel}/...)
+        const afterRelease = parts.slice(4).join('/');
+        if (afterRelease) {
+            urlMap.set(afterRelease, url);
+        }
+        // Filename fallback
+        const basename = path.posix.basename(url.key);
+        if (!urlMap.has(basename)) {
+            urlMap.set(basename, url);
+        }
     }
     // Upload files in batches
     let completed = 0;
@@ -103,7 +113,16 @@ async function uploadFilesWithPresignedUrls(files, urls, options) {
     const uploadFile = async (file) => {
         // Use relativePath for lookup if available, fallback to filename
         const lookupKey = file.relativePath || file.filename;
-        const urlInfo = urlMap.get(lookupKey);
+        let urlInfo;
+        if (file.platform && urlMap.has(`${file.platform}/${lookupKey}`)) {
+            urlInfo = urlMap.get(`${file.platform}/${lookupKey}`);
+        }
+        else if (urlMap.has(lookupKey)) {
+            urlInfo = urlMap.get(lookupKey);
+        }
+        else if (file.filename && urlMap.has(file.filename)) {
+            urlInfo = urlMap.get(file.filename);
+        }
         if (!urlInfo) {
             throw new Error(`No presigned URL found for file: ${lookupKey}`);
         }
@@ -126,6 +145,7 @@ function guessContentType(filename) {
     var _a;
     const ext = (_a = filename.split(".").pop()) === null || _a === void 0 ? void 0 : _a.toLowerCase();
     const contentTypes = {
+        hbc: "application/javascript",
         bundle: "application/javascript",
         js: "application/javascript",
         json: "application/json",
@@ -159,8 +179,9 @@ assetsBaseDir, iosAssetsBaseDir, androidAssetsBaseDir) {
                 type: "bundle",
                 platform: "ios",
                 filename: path.basename(iosBundlePath),
+                relativePath: "ios/" + path.basename(iosBundlePath),
                 localPath: iosBundlePath,
-                contentType: "application/javascript",
+                contentType: guessContentType(iosBundlePath),
                 size: stats.size,
             });
         }
@@ -170,8 +191,9 @@ assetsBaseDir, iosAssetsBaseDir, androidAssetsBaseDir) {
                 type: "bundle",
                 platform: "android",
                 filename: path.basename(androidBundlePath),
+                relativePath: "android/" + path.basename(androidBundlePath),
                 localPath: androidBundlePath,
-                contentType: "application/javascript",
+                contentType: guessContentType(androidBundlePath),
                 size: stats.size,
             });
         }

package/dist/commands/init.d.ts

@@ -0,0 +1,3 @@
+import { Command } from "commander";
+declare const init: Command;
+export default init;