@otalan/cli 1.5.1 → 1.5.3

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to `@otalan/cli` will be documented in this file.
 
+## 1.5.3 - 2026-05-28
+
+### Changed
+
+- Highlight the full active bundle table row in green for interactive `bundles` and rollback output.
+- Print the generated bundle folder after bundle generation.
+
+## 1.5.2 - 2026-05-28
+
+### Changed
+
+- Keep `otalan bundle` output compact by default with publish-style `Bundling` progress and `✅ Bundle created`; detailed bundle context, source-map counts, and JSON output now require `--verbose` or `-v`.
+- Add `-v` as a short alias for verbose publish and bundle output.
+- Print `Bundle selected:` before the rollback bundle summary and `✅ Rollback done` after it.
+- Exit `otalan rollback` without prompting when no bundles are available for the selected tuple.
+
 ## 1.5.1 - 2026-05-26
 
 ### Changed

package/README.md

@@ -350,10 +350,10 @@ 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
+- default output shows compact bundle progress with publish-style status icons, ends with `✅ Bundle created`, and prints the generated bundle folder
+- `--verbose` or `-v` prints the linked project/app, Capacitor build reminder, source-map omitted count, bundle ID source, and JSON bundle result
+- source map files (`*.map`) are omitted from bundle ZIPs by default
 - 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
 - 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
 
@@ -432,7 +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
+- default output shows compact publish progress with animated terminal status icons; `--verbose` or `-v` 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
@@ -502,6 +502,8 @@ Lists remote bundles for the current app so you can choose a bundle for rollback
 
 Remote bundle tables display the API `publishedAt` timestamp, not the bundle row `createdAt` timestamp.
 
+In interactive terminals, the active bundle row is highlighted in green.
+
 Default resolution order:
 
 1. `--runtime-version`
@@ -523,6 +525,8 @@ Reactivates an older bundle for the same tuple.
 otalan rollback --bundle-id 1.0.0-web.1 --platform ios --channel production
 ```
 
+When no bundles exist for the selected platform, channel, and runtimeVersion, `otalan rollback` exits without prompting for a target bundle. Successful rollbacks print `Bundle selected:`, the selected bundle summary, and then `✅ Rollback done`.
+
 ### `otalan pause`
 
 Pauses delivery of the currently active bundle for the selected release tuple.