@otalan/cli 1.4.0 → 1.5.0

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 All notable changes to `@otalan/cli` will be documented in this file.
 
+## 1.5.0 - 2026-05-23
+
+### Added
+
+- Add `otalan channels` to print the resolved organization/project context and list project release channels with their apps from `GET /v1/releases/channels`; it supports `--app-id`, and interactive runs default to `All` before optionally filtering by app.
+
+### Changed
+
+- Document Expo SDK 56 as officially supported.
+
+### Fixed
+
+- Avoid Bun worker ZIP compression failures when packaging large Expo export assets.
+
+## 1.4.1 - 2026-05-22
+
+### Changed
+
+- Hide interactive OTA Publish Key input during `otalan login` and validate credentials before saving them.
+- Surface skipped duplicate-bundle checks, non-JSON API error bodies, and truncated bundle table cells more clearly.
+- Harden direct uploads, argument parsing, global config permissions, Expo CLI resolution, and Expo runtime metadata scanning.
+
 ## 1.4.0 - 2026-05-22
 
 ### Changed

package/README.md

@@ -9,7 +9,7 @@ Published as an npm package, but the CLI itself runs on Bun.
 ## Requirements
 
 - Bun `>= 1.3.11` installed and available on your `PATH`
-- An Otalan **OTA Publish Key** for commands that talk to the Otalan API
+- An Otalan **OTA Publish Key**, generated from the Otalan Dashboard, for commands that talk to the Otalan API
 
 Otalan key prefixes are stable API identifiers:
 
@@ -31,7 +31,7 @@ The npm package ships a Bun-based CLI entrypoint, not standalone native binaries
 Officially supported app targets and versions:
 
 - Capacitor 7 and 8 with `--target capacitor`
-- Expo SDK 54 and 55 with `--target expo`
+- Expo SDK 54, 55, and 56 with `--target expo`
 
 Other app targets and older framework versions may work, but they are not officially supported for the moment.
 
@@ -339,7 +339,7 @@ otalan bundle --target expo --platform ios
 
 Current behavior:
 
-- Official support covers Capacitor 7 and 8, and Expo SDK 54 and 55
+- Official support covers Capacitor 7 and 8, and Expo SDK 54, 55, and 56
 - Other app targets and older framework versions may work, but they are not officially supported for the moment
 - Capacitor packages prebuilt web assets; it does not run your app build command
 - without `--input-dir`, Capacitor checks `dist/` first and then `www/`
@@ -362,6 +362,8 @@ Runtime version defaults:
 - 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
 
+Native project file parsing is best-effort. If your `Info.plist`, Xcode build settings, or Gradle files use patterns the CLI cannot read, pass `--runtime-version` explicitly.
+
 For Expo projects, the recommended app config is:
 
 ```json
@@ -429,6 +431,7 @@ Current behavior:
 - `--release-notes` attaches release notes to the published bundle
 - Expo publish forwards the full generated Otalan satellite manifest when present
 - Expo publish sends the generated manifest with `runtimeVersion`
+- Expo manifests include the Expo config captured from `bunx expo config --json`; avoid placing secrets in Expo config fields that are not intended to be uploaded
 - Otalan validates the release ZIP before the publish completes
 - active rollouts can be paused and resumed later without changing the selected bundle
 
@@ -463,6 +466,32 @@ The ZIP is opened as a disk-backed `Bun.file` and passed directly to the returne
 
 If validation fails, `otalan publish` exits non-zero and prints the ingest failure reason when the API provides one. This makes the command safe to use directly in CI/CD pipelines.
 
+### `otalan channels`
+
+Prints the resolved organization/project context, then lists distinct release channels for the project resolved from the configured OTA Publish Key. This command does not require `otalan init`.
+
+```bash
+otalan channels
+otalan channels --app-id com.example.app
+```
+
+When `--app-id` is omitted in an interactive terminal, the CLI prompts for an app filter with `All` selected by default. Non-interactive runs default to `All`.
+
+The command uses `GET /v1/releases/channels`, optionally with `?appId=...`, and prints each returned channel with the apps that use it:
+
+```json
+{
+  "items": [
+    {
+      "channel": "production",
+      "apps": [
+        { "appId": "com.example.app", "name": "Example App" }
+      ]
+    }
+  ]
+}
+```
+
 ### `otalan bundles`
 
 Lists remote bundles for the current app so you can choose a bundle for rollback or rollout operations.