@otalan/cli 1.2.2 → 1.3.1

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to `@otalan/cli` will be documented in this file.
 
+## 1.3.1 - 2026-05-18
+
+### Added
+
+- Check for an already published bundle ID during `otalan bundle` when auth and project config are available.
+
+## 1.3.0 - 2026-05-18
+
+### Added
+
+- Validate Capacitor and Expo bundle contents before writing output, rejecting native project/source files in OTA bundle data.
+
+### Changed
+
+- Use `runtimeVersion` as the only bundle manifest, CLI option, and release API field for both Capacitor and Expo.
+
 ## 1.2.2 - 2026-05-13
 
 ### Changed
@@ -25,7 +41,7 @@ All notable changes to `@otalan/cli` will be documented in this file.
 - Switch `otalan publish` to the direct-upload release contract: create JSON upload metadata, upload the ZIP to the returned opaque `uploadUrl`, complete the ingest, then poll validation.
 - Stream the local ZIP through Bun's disk-backed file body during direct uploads instead of loading the full archive into memory.
 - Send the full generated Otalan Expo satellite manifest as `expoManifest` during publish instead of only raw Expo config.
-- Use the Expo `runtimeVersion` as the release `nativeVersion` sent to the API, matching the current Expo update matching contract.
+- Use the Expo `runtimeVersion` as the release version sent to the API, matching the current Expo update matching contract.
 - Use the release bundle `publishedAt` timestamp for bundle lists, status summaries, rollback prompts, and published bundle ID hints.
 
 ## 1.1.1 - 2026-05-07
@@ -45,7 +61,7 @@ All notable changes to `@otalan/cli` will be documented in this file.
 
 - Let `otalan login` reuse the saved API URL and keep the saved CI key from a masked prompt.
 - Export Expo bundles into a project-local `.otalan/expo-export-*` folder so Expo accepts the output path.
-- Fall back to the resolved native version when Expo runtimeVersion is not configured or present in export metadata.
+- Fall back to the resolved app version when Expo runtimeVersion is not configured or present in export metadata.
 - Clarify Capacitor and Expo bundling behavior in CLI help and README.
 
 ## 1.0.9 - 2026-05-06
@@ -88,7 +104,7 @@ All notable changes to `@otalan/cli` will be documented in this file.
 
 ### Added
 
-- Prompt interactively for bundle native version and bundle ID, with hints for the detected native version, local bundle ID, and active published bundle ID when available.
+- Prompt interactively for bundle runtime version and bundle ID, with hints for the detected runtime version, local bundle ID, and active published bundle ID when available.
 
 ### Changed
 
@@ -124,5 +140,5 @@ Initial public release of the Otalan CLI.
 - Release publishing with rollout metadata and server-side validation polling.
 - Bundle listing, active bundle status, and rollback commands.
 - CI key login, project initialization, and API connectivity doctor checks.
-- Native version and Expo runtime version resolution helpers.
+- Runtime version resolution helpers.
 - Public npm package metadata, license notices, and Bun-based CLI entrypoint.

package/README.md

@@ -222,7 +222,7 @@ Example project config:
 }
 ```
 
-`otalan.config.json` only links the repo to an Otalan project/app. Bundle and release targeting data such as `target`, `platform`, `nativeVersion`, `runtimeVersion`, and `bundleId` live in `.otalan/bundle/manifest.json`.
+`otalan.config.json` only links the repo to an Otalan project/app. Bundle and release targeting data such as `target`, `platform`, `runtimeVersion`, and `bundleId` live in `.otalan/bundle/manifest.json`.
 
 ## Command Reference
 
@@ -338,17 +338,17 @@ Current behavior:
 - Expo stores the generated Otalan satellite manifest in `.otalan/bundle/manifest.json`, including `launchAsset`, `assets`, `runtimeVersion`, `bundleId`, and `expoConfig`
 - both outputs produce a ZIP plus `manifest.json`
 - source map files (`*.map`) are omitted from bundle ZIPs by default; the CLI prints the omitted file count when any are skipped
-- `--platform` is required so the CLI exports the selected platform and resolves the correct native/runtime version
+- native project/source files are rejected before bundle output is written; OTA bundles must only contain generated web/update assets
+- when `otalan login` and `otalan init` are configured, the CLI checks that the selected `bundleId` is not already published for the selected platform, runtimeVersion, and channel before writing bundle output
+- `--platform` is required so the CLI exports the selected platform and resolves the correct runtime version
 
-Native version defaults:
+Runtime version defaults:
 
-- In an interactive terminal, `otalan bundle` prompts for the native version after showing the detected active native version.
-- Capacitor iOS reads `CFBundleShortVersionString` from `Info.plist` and resolves `$(MARKETING_VERSION)` from the Xcode project when needed
-- Capacitor Android reads `versionName` from `android/app/build.gradle` or `build.gradle.kts`
-- Expo reads the selected platform version from Expo config and falls back to the top-level Expo `version`
-- Expo runtimeVersion reads `--runtime-version`, Expo export metadata, or Expo config runtimeVersion policies/strings; if none are present, the CLI falls back to the resolved native version
-- Expo publishes use `runtimeVersion` as the Otalan release `nativeVersion` because Expo update checks send `expo-runtime-version`
-- `--native-version` overrides auto-detection
+- In an interactive terminal, `otalan bundle` prompts for the runtime version after showing the detected active runtime version.
+- Capacitor iOS defaults runtimeVersion from `CFBundleShortVersionString` in `Info.plist` and resolves `$(MARKETING_VERSION)` from the Xcode project when needed
+- Capacitor Android defaults runtimeVersion from `versionName` in `android/app/build.gradle` or `build.gradle.kts`
+- Expo runtimeVersion reads `--runtime-version`, Expo export metadata, or Expo config runtimeVersion policies/strings; if none are present, the CLI falls back to the selected platform Expo `version`
+- `--runtime-version` overrides auto-detection
 
 For Expo projects, the recommended app config is:
 
@@ -385,10 +385,11 @@ otalan bundle --target expo --platform ios --bundle-id 1.0.5
 If you omit `bundleId`:
 
 - in an interactive terminal, the CLI prompts for a bundle ID and shows the local bundle ID from `.otalan/bundle/manifest.json` when available
-- when `otalan login` and `otalan init` are configured, the prompt also shows the active published bundle ID for the selected platform/native version/channel
+- when `otalan login` and `otalan init` are configured, the prompt also shows the active published bundle ID for the selected platform/runtime version/channel
 - published bundle hints use `--channel`, defaulting to `production`
+- duplicate published bundle ID checks use the same `--channel` value and default to `production`
 - pressing Enter without a bundle ID keeps the automatic bundle ID behavior
-- the CLI reads `nativeVersion` from the selected native platform and adds a short hash suffix
+- the CLI reads `runtimeVersion` from the selected platform and adds a short hash suffix
 - example: `1.0.0-abc123def456`
 
 If you want to take the bundle ID from `package.json` instead:
@@ -402,20 +403,20 @@ otalan bundle --target expo --platform ios --bundle-from-package
 
 Publishes the current bundle output with rollout metadata.
 
-`otalan publish` uses the `bundleId`, `platform`, and release version stored in `.otalan/bundle/manifest.json`. Capacitor uses `nativeVersion`; Expo uses `runtimeVersion`. To release `1.0.5`, set it when you run `otalan bundle --bundle-id 1.0.5`.
+`otalan publish` uses the `bundleId`, `platform`, and `runtimeVersion` stored in `.otalan/bundle/manifest.json`. To release `1.0.5`, set it when you run `otalan bundle --bundle-id 1.0.5`.
 
 Current behavior:
 
 - `channel` is chosen at publish time
 - publishes are mandatory by default
 - default rollout is `100`
-- `--platform` and `--native-version` can override the manifest, but only if they match it
+- `--platform` and `--runtime-version` can override the manifest, but only if they match it
 - `--output-dir` lets you publish a bundle from a non-default folder
 - `--rollout-percent` accepts an integer from `0` to `100`
 - `--optional` marks the update as non-mandatory
 - `--release-notes` attaches release notes to the published bundle
 - Expo publish forwards the full generated Otalan satellite manifest when present
-- Expo publish sends `runtimeVersion` as the API `nativeVersion` and normalizes the serialized `expoManifest.nativeVersion` to the same value for server validation
+- Expo publish sends the generated manifest with `runtimeVersion`
 - Otalan validates the release ZIP before the publish completes
 - active rollouts can be paused and resumed later without changing the selected bundle
 
@@ -458,9 +459,9 @@ Remote bundle tables display the API `publishedAt` timestamp, not the bundle row
 
 Default resolution order:
 
-1. `--native-version`
+1. `--runtime-version`
 2. `.otalan/bundle/manifest.json` if present and the manifest platform matches the selected platform
-3. native version derived from the selected platform in the local app project
+3. runtime version derived from the selected platform in the local app project
 4. interactive prompt
 
 ```bash
@@ -471,7 +472,7 @@ otalan bundles --platform ios --channel production
 
 Reactivates an older bundle for the same tuple.
 
-`rollback` uses the same native-version default order as `bundles`. Pass `--native-version` if you want to override the detected default.
+`rollback` uses the same runtime-version default order as `bundles`. Pass `--runtime-version` if you want to override the detected default.
 
 ```bash
 otalan rollback --bundle-id 1.0.0-web.1 --platform ios --channel production
@@ -481,7 +482,7 @@ otalan rollback --bundle-id 1.0.0-web.1 --platform ios --channel production
 
 Pauses delivery of the currently active bundle for the selected release tuple.
 
-`pause` uses the same native-version default order as `bundles`. The active bundle remains selected, but new OTA checks stop receiving it until you resume the rollout.
+`pause` uses the same runtime-version default order as `bundles`. The active bundle remains selected, but new OTA checks stop receiving it until you resume the rollout.
 
 ```bash
 otalan pause --platform ios --channel production
@@ -491,7 +492,7 @@ otalan pause --platform ios --channel production
 
 Resumes delivery of the currently active bundle for the selected release tuple.
 
-`resume` uses the same native-version default order as `bundles`.
+`resume` uses the same runtime-version default order as `bundles`.
 
 ```bash
 otalan resume --platform ios --channel production
@@ -503,7 +504,7 @@ Shows the active bundle for the selected release tuple.
 
 The active bundle summary displays `publishedAt` as `Published at`.
 
-`status` also uses the same native-version default order as `bundles`.
+`status` also uses the same runtime-version default order as `bundles`.
 
 ```bash
 otalan status --platform ios --channel production
@@ -517,7 +518,7 @@ otalan status --platform ios --channel production
 {
   "target": "capacitor",
   "hash": "sha256...",
-  "nativeVersion": "1.0.0",
+  "runtimeVersion": "1.0.0",
   "bundleId": "1.0.0-abcdef123456",
   "createdAt": "2026-04-07T12:00:00.000Z",
   "platform": "ios"
@@ -530,7 +531,6 @@ otalan status --platform ios --channel production
 {
   "target": "expo",
   "hash": "sha256...",
-  "nativeVersion": "1.0.0",
   "runtimeVersion": "1.0.0",
   "bundleId": "1.0.0-abcdef123456",
   "launchAsset": "bundles/ios-xxxxx.js",