@wix/himalaya-cli 0.1482.0 → 0.1483.0

package/guides/qa-builds.md

@@ -1095,6 +1095,28 @@ himi dist --app <app> --platform android --aab --wait --target bo
   `DIST_ANDROID_FORMAT=aab` in its environment no longer turns an APK job into a bundle; the check
   stays for a runner older than that rule. A later delivery that passes every check (a retry on a
   clean machine) clears the verdict.
+- **A Containers app's bundle is a store build.** For an app bound to a Wix site, the bundle is the
+  file its owner uploads to Google Play, so it is checked last before the build starts: the caller
+  owns the app's site (a self-serve caller's only path to a bundle; any other self-serve `--aab` is
+  `403 android_format_not_allowed`) (the `--signing byo` check, so `--aab` sends your Wix login), the app holds its
+  site's store app (`PUT /v1/admin/site/store-app`), and Wix agrees (`ValidateStoreBuild`: a package
+  name is saved, and the site's plan allows publishing the app yourself). That check locks the
+  package name at the app's first store build, and the bundle is built under it. Refusals:
+  `store_build_android_only`, `store_build_incompatible_options` (`--signing byo`) and
+  `store_build_shell_unsupported` (any shell but `branded-lite`, the one that both builds under the
+  contract's applicationId and targets the API level Google Play requires) 400, `store_build_site_forbidden` 403,
+  `store_id_missing`, `store_app_site_taken`, `premium_plan_required` and
+  `release_predates_store_builds` (the release was built from a commit older than store builds, so
+  its bundle would fail or Play would refuse it; checked before the name is locked — publish a new
+  release and build again) 409,
+  `store_builds_unconfigured` 501, `store_builds_unavailable` 503 (also when the app's site binding
+  cannot be read, or Wix answers no usable package name). Each refusal carries `code`, equal to
+  `error`.
+  The same checks are available WITHOUT a build, for the Containers editor to ask before it
+  activates a draft release: `GET /v1/admin/site/store-build-check?app=&site=[&shell=]` answers
+  `200 { ok: true, android: { packageName } }` or the same refusals, through `ValidateStoreBuild`'s
+  check-only mode, so it locks nothing. Until that mode is wired it answers
+  `501 store_builds_unconfigured`; it never falls back to the locking call.
 
 **Why the Wix production key, and only for the bundle.** There are two Android keys: the committed
 QA keystore and the Wix production key (WixOne). WixOne is the Play **upload** key every Branded

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1482.0",
+  "version": "0.1483.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "fd8ba72a1838f65e8e437d82939b1734daa3b07881672fd7f2604e4e"
+  "falconPackageHash": "e7f0dcc8dff51ebc6c4145c1a3a2fbb2346a063b5a972db85e258c8d"
 }