@wix/himalaya-cli 0.1553.0 → 0.1554.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.mjs +0 -1
- package/guides/qa-builds.md +9 -6
- package/package.json +2 -2
package/dist/cli.mjs
CHANGED
|
@@ -12882,7 +12882,6 @@ function webViewOriginAllowed(url, origins) {
|
|
|
12882
12882
|
}
|
|
12883
12883
|
var init_webview_origin = __esm({
|
|
12884
12884
|
"../../core/ts/src/webview-origin.ts"() {
|
|
12885
|
-
"use strict";
|
|
12886
12885
|
}
|
|
12887
12886
|
});
|
|
12888
12887
|
|
package/guides/qa-builds.md
CHANGED
|
@@ -1169,9 +1169,12 @@ himi dist --app <app> --platform android --aab --wait --target bo
|
|
|
1169
1169
|
file its owner uploads to Google Play, so it is checked last before the build starts: the caller
|
|
1170
1170
|
owns the app's site (a self-serve caller's only path to a bundle; any other self-serve `--aab` is
|
|
1171
1171
|
`403 android_format_not_allowed`) (the `--signing byo` check, so `--aab` sends your Wix login), the app holds its
|
|
1172
|
-
site's store app (`PUT /v1/admin/site/store-app`), and Wix agrees (`
|
|
1173
|
-
name is saved, and the site's plan allows publishing the app yourself). That check locks the
|
|
1174
|
-
package name at the app's first store build, and the bundle is built under it.
|
|
1172
|
+
site's store app (`PUT /v1/admin/site/store-app`), and Wix agrees (`CreateBuildRecordIfAllowed`: a
|
|
1173
|
+
package name is saved, and the site's plan allows publishing the app yourself). That check locks the
|
|
1174
|
+
package name at the app's first store build, and the bundle is built under it. It also opens Wix's
|
|
1175
|
+
record of the build, which the job id and then the result (status, version, bundle) are reported to
|
|
1176
|
+
(`UpdateStoreBuild`); a build that never reaches the pool closes its record as failed. A report that
|
|
1177
|
+
fails is sent again on a later read and never fails the build. Refusals:
|
|
1175
1178
|
`store_build_android_only`, `store_build_incompatible_options` (`--signing byo`) and
|
|
1176
1179
|
`store_build_shell_unsupported` (any shell but `branded-lite`, the one that both builds under the
|
|
1177
1180
|
contract's applicationId and targets the API level Google Play requires) 400, `store_build_site_forbidden` 403,
|
|
@@ -1184,8 +1187,8 @@ himi dist --app <app> --platform android --aab --wait --target bo
|
|
|
1184
1187
|
`error`.
|
|
1185
1188
|
The same checks are available WITHOUT a build, for the Containers editor to ask before it
|
|
1186
1189
|
activates a draft release: `GET /v1/admin/site/store-build-check?app=&site=[&shell=]` answers
|
|
1187
|
-
`200 { ok: true, android: { packageName } }` or the same refusals, through `
|
|
1188
|
-
|
|
1190
|
+
`200 { ok: true, android: { packageName } }` or the same refusals, through `CheckIfBuildIsAllowed`,
|
|
1191
|
+
so it locks nothing. It names no release, so it cannot give
|
|
1189
1192
|
`409 release_predates_store_builds`; a draft the editor just built is on a current commit. It never
|
|
1190
1193
|
falls back to the locking call.
|
|
1191
1194
|
- **A Containers app's TestFlight build is an App Store build.** For an app bound to a Wix site,
|
|
@@ -1194,7 +1197,7 @@ himi dist --app <app> --platform android --aab --wait --target bo
|
|
|
1194
1197
|
in mobile-apps-containers-builder, and uploaded to the owner's TestFlight with the owner's App
|
|
1195
1198
|
Store Connect key. The checks run last before the build starts: the caller owns the app's site
|
|
1196
1199
|
(send your Wix login, as for a bundle), the app holds its site's store app, the release's commit
|
|
1197
|
-
can make one (`appStoreBuild` in the signing marker), `
|
|
1200
|
+
can make one (`appStoreBuild` in the signing marker), `CheckIfBuildIsAllowed` finds a
|
|
1198
1201
|
saved bundle id and an eligible plan (so an ineligible site never reaches Apple), then
|
|
1199
1202
|
`PrepareAppleCertificates` registers the bundle id in the owner's Apple account and answers the
|
|
1200
1203
|
certificate, profile and key, and only then `ValidateStoreBuild` locks the bundle id (so a bundle id
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/himalaya-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.1554.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"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.",
|
|
6
6
|
"keywords": [
|
|
@@ -71,5 +71,5 @@
|
|
|
71
71
|
"artifactId": "himalaya-cli"
|
|
72
72
|
}
|
|
73
73
|
},
|
|
74
|
-
"falconPackageHash": "
|
|
74
|
+
"falconPackageHash": "0deddde2b736534ceb92eb41916db4c25627469d9d6f9c427ab48004"
|
|
75
75
|
}
|