@wix/referral 1.0.53 → 1.0.54

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/referral",
-  "version": "1.0.53",
+  "version": "1.0.54",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
@@ -23,7 +23,7 @@
   "dependencies": {
     "@wix/referral_customers": "1.0.18",
     "@wix/referral_friends": "1.0.22",
-    "@wix/referral_programs": "1.0.28",
+    "@wix/referral_programs": "1.0.29",
     "@wix/referral_rewards": "1.0.17",
     "@wix/referral_tracker": "1.0.22"
   },
@@ -50,5 +50,5 @@
       "fqdn": ""
     }
   },
-  "falconPackageHash": "2f813136d90e7033922d7a275dcb4d773991a7223cf81cfd7daf0074"
+  "falconPackageHash": "8dc9252b383b4aed25e23ad8175ae52e3b5c5937151053fc99f5d236"
 }

package/type-bundles/context.bundle.d.ts

@@ -1060,6 +1060,21 @@ interface SiteMarkedAsTemplate {
 }
 interface SiteMarkedAsWixSite {
 }
+/**
+ * Represents a service provisioned a site.
+ *
+ * Note on `origin_instance_id`:
+ * There is no guarantee that you will be able to find a meta site using `origin_instance_id`.
+ * This is because of the following scenario:
+ *
+ * Imagine you have a template where a third-party application (TPA) includes some stub data,
+ * such as a product catalog. When you create a site from this template, you inherit this
+ * default product catalog. However, if the template's product catalog is modified,
+ * your site will retain the catalog as it was at the time of site creation. This ensures that
+ * your site remains consistent with what you initially received and does not include any
+ * changes made to the original template afterward.
+ * To ensure this, the TPA on the template gets a new instance_id.
+ */
 interface ServiceProvisioned {
     /** Either UUID or EmbeddedServiceType. */
     appDefId?: string;

package/type-bundles/index.bundle.d.ts

@@ -1060,6 +1060,21 @@ interface SiteMarkedAsTemplate {
 }
 interface SiteMarkedAsWixSite {
 }
+/**
+ * Represents a service provisioned a site.
+ *
+ * Note on `origin_instance_id`:
+ * There is no guarantee that you will be able to find a meta site using `origin_instance_id`.
+ * This is because of the following scenario:
+ *
+ * Imagine you have a template where a third-party application (TPA) includes some stub data,
+ * such as a product catalog. When you create a site from this template, you inherit this
+ * default product catalog. However, if the template's product catalog is modified,
+ * your site will retain the catalog as it was at the time of site creation. This ensures that
+ * your site remains consistent with what you initially received and does not include any
+ * changes made to the original template afterward.
+ * To ensure this, the TPA on the template gets a new instance_id.
+ */
 interface ServiceProvisioned {
     /** Either UUID or EmbeddedServiceType. */
     appDefId?: string;