@wix/himalaya-cli 0.810.0 → 0.812.0

package/dist/cli.mjs

@@ -445,7 +445,7 @@ var WIX_COLLECTION_ID_MAX_LENGTH, SAFE_APP_ID, KV_NAME;
 var init_ownership = __esm({
   "../../core/data-resources/src/ownership.ts"() {
     init_schema();
-    WIX_COLLECTION_ID_MAX_LENGTH = 36;
+    WIX_COLLECTION_ID_MAX_LENGTH = 256;
     SAFE_APP_ID = /^[a-z0-9]+(?:-[a-z0-9]+)*(?:\.[a-z0-9]+(?:-[a-z0-9]+)*)?$/;
     KV_NAME = /^[a-z0-9]+(?:-[a-z0-9]+)*$/;
   }
@@ -11459,6 +11459,7 @@ function shouldRevealError(args) {
 var EMAIL_RE, URL_HOST_RE, INTEGER_RE, NUMBER_RE;
 var init_validation = __esm({
   "../../core/ts/src/validation.ts"() {
+    "use strict";
     EMAIL_RE = /^[A-Za-z0-9._%+-]+@[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*\.[A-Za-z]{2,}$/;
     URL_HOST_RE = /^[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*(:[0-9]+)?$/;
     INTEGER_RE = /^[+-]?[0-9]+$/;
@@ -14804,6 +14805,7 @@ function validateWorkerSubtree(raw, slotId, policy, actionCatalog) {
 var WORKER_SUBTREE_CEILINGS, ID_PART, ACTION_ID;
 var init_worker_subtree = __esm({
   "../../core/ts/src/worker-subtree.ts"() {
+    "use strict";
     init_worker_subtree_safe_types_generated();
     WORKER_SUBTREE_CEILINGS = Object.freeze({
       maxEncodedBytes: 65536,

package/guides/cms-collections.md

@@ -43,27 +43,32 @@ Two constraints exist because a bare prefix is **not** a namespace, and both are
   would genuinely own one namespace and whichever ran `cms create` last would reconcile the
   others' schemas to its own declaration.
 
-**The whole id is capped at 36 characters**, and this one is a Wix Data limit rather than a
-Himalaya rule: no naming choice removes the cap, though naming choices decide how much of it
-you spend. It applies to `himi_<appSlug>_<name>` in full — the arithmetic is
-`prefix + <name> ≤ 36` — and the prefix is longer than it looks because it already carries
-`himi_` and a trailing `_`. Since the prefix is folded from the app id, a shorter app id
-leaves more room; an app id carrying a timestamp or an owner prefix eats most of the budget on
-its own:
+**The whole id is capped at 256 characters**, and this one is a Wix Data limit rather than a
+Himalaya rule: `DataCollection.id` is published as `maxLength: 256` on
+[Create Data Collection](https://dev.wix.com/docs/api-reference/business-solutions/cms/collection-management/data-collections/create-data-collection),
+which is the call `himi cms create` makes. It applies to `himi_<appSlug>_<name>` in full,
+prefix included. In practice it does not bind — even an app id carrying a timestamp and an
+owner prefix leaves the suffix well over two hundred characters:
 
 ```
-himi_cadence_20260915_122324_3_          31 characters, leaving 5
-himi_cadence_20260915_122324_3_entries   38 — refused
+himi_cadence_20260915_122324_3_          31 characters
+himi_cadence_20260915_122324_3_entries   38 — accepted, far inside the cap
 ```
 
-That is most of the budget gone before you have named anything, so pick both the app id and
-the `<name>` with the cap in mind — before provisioning, because renaming an app that already
-owns collections changes the namespace and means a migration.
+> **himi enforced 36 characters here until this was corrected.** That number arrived with a
+> starter app and was traceable to no Wix source — it is a UUID's length. So `himi validate`
+> refused ids Wix accepts, and the report that looked like proof of a 36-character limit — the
+> 38-character `..._entries` id above — was himi's own refusal rather than a Wix rejection. If
+> you find an older note budgeting a 36-character id, it is wrong.
+
+Renaming an app that already owns collections changes the namespace and means a migration, so
+still pick the app id before you provision — you just no longer have to pick it *short*.
 
 `himi validate` is what refuses an over-long id locally, naming the count and the cap. The
 mutating verbs do **not** re-check it — `cms create` and `cms seed` verify only that the id
-carries the app's prefix — so validate before you provision rather than finding out at the
-Wix call.
+carries the app's prefix — so an id over the cap reaches Wix and is refused there instead of
+locally. At 256 characters you have to work to build one. Note that while himi enforced 36
+this gap could not bite at all: every id it let through was an id Wix accepts.
 
 Every role is validated against the supported values too — an unrecognized role used to be
 forwarded to Wix verbatim, and `writeRole: "ANYONE"` would have let anyone on the internet

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.810.0",
+  "version": "0.812.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": [
@@ -63,5 +63,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "d6be6663118a9f9388db120025b462345688759f637c5d760c06010d"
+  "falconPackageHash": "65ec344515508714eab1eee898f49b670f2ad738a0690a7a4dde7ed1"
 }