@wix/himalaya-cli 0.1443.0 → 0.1444.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/guides/qa-builds.md +20 -0
- package/package.json +2 -2
package/guides/qa-builds.md
CHANGED
|
@@ -327,6 +327,26 @@ It **fails open** throughout: an outage, a rate limit, a missing or revoked toke
|
|
|
327
327
|
simply not being able to tell — all dispatch as before. Without `HIMI_DIST_GITHUB_TOKEN` the check
|
|
328
328
|
is off entirely.
|
|
329
329
|
|
|
330
|
+
### Telling a signing failure from a build failure — `failureCode`
|
|
331
|
+
|
|
332
|
+
`error` is free text for a human; never parse it. A surface that shows a different message per kind
|
|
333
|
+
reads `failureCode` on the job (`himi dist status`, `GET /v1/admin/dist/{jobId}`, the list):
|
|
334
|
+
|
|
335
|
+
- **`signing`** — Himalaya could not mint an iOS identity the build needs: `/v1/dist/signing`
|
|
336
|
+
answered `apple_signing_failed` (for the app or an embedded bundle), or a customer signing fetch
|
|
337
|
+
failed. A *refused* `?embedded=` (a 4xx) does not count: the build continues without that bundle.
|
|
338
|
+
- **absent** — any other failure, or none.
|
|
339
|
+
|
|
340
|
+
It is written when the signing request is answered, so it lands while the job is still `WORKING`:
|
|
341
|
+
read it only once `status` is `FAILURE`. A Job Service retry clears it once its app identity is
|
|
342
|
+
minted, or when it ends `SUCCESS`. It misses a signing error raised on the Mac after the identity
|
|
343
|
+
arrived (a keychain or profile install), which then reads as a plain failure.
|
|
344
|
+
|
|
345
|
+
A build that throws after the build step — an S3 upload, say — reports `FAILURE` too, with
|
|
346
|
+
`error: "dist failed: …"`. Before, the pool exited 0 having reported nothing, and the job ended
|
|
347
|
+
`SUCCESS` with no artifact. When a failure report cannot be delivered at all, the job exits
|
|
348
|
+
non-zero, so Job Service records the failure itself.
|
|
349
|
+
|
|
330
350
|
### Which commit the pool builds, and what off-repo gets
|
|
331
351
|
|
|
332
352
|
Three sources, in order. The caller is absent from the list on purpose — a caller-chosen sha would
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wix/himalaya-cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.1444.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": "2a5ac67ab4d6220139d0677bf644bedad760540b43889fe55394e090"
|
|
75
75
|
}
|