@wix/automations 1.0.81 → 1.0.82

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/automations",
-  "version": "1.0.81",
+  "version": "1.0.82",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",
     "access": "public"
@@ -22,8 +22,8 @@
   ],
   "dependencies": {
     "@wix/automations_activations": "1.0.50",
-    "@wix/automations_automations-service": "1.0.36",
-    "@wix/automations_automations-service-v-2": "1.0.49"
+    "@wix/automations_automations-service": "1.0.37",
+    "@wix/automations_automations-service-v-2": "1.0.50"
   },
   "devDependencies": {
     "glob": "^10.4.1",
@@ -48,5 +48,5 @@
       "fqdn": ""
     }
   },
-  "falconPackageHash": "d99e02e1366c7b1a3cd7253d53d8ea2cc3dd501447be7b42cc26d82d"
+  "falconPackageHash": "db50912d5b02062004ae220939c319699614f78447adecb3be71d50b"
 }

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

@@ -1147,6 +1147,21 @@ interface SiteMarkedAsTemplate$1 {
 }
 interface SiteMarkedAsWixSite$1 {
 }
+/**
+ * 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$1 {
     /** Either UUID or EmbeddedServiceType. */
     appDefId?: string;
@@ -5183,6 +5198,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

@@ -1147,6 +1147,21 @@ interface SiteMarkedAsTemplate$1 {
 }
 interface SiteMarkedAsWixSite$1 {
 }
+/**
+ * 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$1 {
     /** Either UUID or EmbeddedServiceType. */
     appDefId?: string;
@@ -5183,6 +5198,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;