@otalan/cli 1.4.1 → 1.5.1

package/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 All notable changes to `@otalan/cli` will be documented in this file.
 
+## 1.5.1 - 2026-05-26
+
+### Changed
+
+- Make `otalan publish` show compact animated progress by default, with green success and red failure states in interactive terminals.
+- Add spacing around compact publish progress and highlight `Live` in green in interactive terminals.
+- Keep CI-friendly static publish progress output in non-TTY environments.
+- Move the previous detailed publish output behind `otalan publish --verbose`.
+- Print `✅ Bundle generated` after `otalan bundle` writes the bundle output.
+
+## 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

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.
 
@@ -282,6 +282,8 @@ Saves the project OTA Publish Key and API base URL locally.
 
 If auth is already saved, `otalan login` shows the current API URL as the prompt default and shows the current OTA Publish Key in masked form. Press Enter to keep either value.
 
+During interactive login, typed OTA Publish Key characters are echoed as `*` so the terminal shows input progress without exposing the key.
+
 ```bash
 otalan login --api-key otalan_ci_xxx --api-url https://api.otalan.com
 ```
@@ -339,7 +341,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/`
@@ -348,6 +350,7 @@ Current behavior:
 - Expo does not require a prebuilt `dist/` or `www/` folder
 - 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`
+- successful bundle runs end with `✅ Bundle generated`
 - source map files (`*.map`) are omitted from bundle ZIPs by default; the CLI prints the omitted file count when any are skipped
 - native project/source files are rejected before bundle output is written; OTA bundles must only contain generated web/update assets
 - when `otalan.config.json` is available, the CLI prints the linked project and app before packaging
@@ -429,6 +432,7 @@ Current behavior:
 - `--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
+- default output shows compact publish progress with animated terminal status icons; `--verbose` prints the full project, release, and ingest details
 - 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
@@ -466,6 +470,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.