@zernio/node 0.2.846 → 0.2.847

package/dist/index.d.mts

@@ -35206,6 +35206,10 @@ type DuplicateAdData = {
         renamePrefix?: string;
         renameSuffix?: string;
         syncAfter?: boolean;
+        /**
+         * Point the copy at the source ad's creative object instead of copying it, so the copy keeps the same Facebook post, the same Instagram media, their existing likes, comments and shares, and the full creative setup (text variations included). This is what Ads Manager's "show existing reactions, comments and shares" does. Meta's native copy always publishes new posts. A creative belongs to one ad account, so `adSetId` must be in the source ad's account. 400 when the source ad has no creative yet.
+         */
+        reuseSourceCreative?: boolean;
     };
     headers?: {
         /**

package/dist/index.d.ts

@@ -35206,6 +35206,10 @@ type DuplicateAdData = {
         renamePrefix?: string;
         renameSuffix?: string;
         syncAfter?: boolean;
+        /**
+         * Point the copy at the source ad's creative object instead of copying it, so the copy keeps the same Facebook post, the same Instagram media, their existing likes, comments and shares, and the full creative setup (text variations included). This is what Ads Manager's "show existing reactions, comments and shares" does. Meta's native copy always publishes new posts. A creative belongs to one ad account, so `adSetId` must be in the source ad's account. 400 when the source ad has no creative yet.
+         */
+        reuseSourceCreative?: boolean;
     };
     headers?: {
         /**

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.846",
+  version: "0.2.847",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.846",
+  version: "0.2.847",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zernio/node",
-  "version": "0.2.846",
+  "version": "0.2.847",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -35590,6 +35590,10 @@ export type DuplicateAdData = {
         renamePrefix?: string;
         renameSuffix?: string;
         syncAfter?: boolean;
+        /**
+         * Point the copy at the source ad's creative object instead of copying it, so the copy keeps the same Facebook post, the same Instagram media, their existing likes, comments and shares, and the full creative setup (text variations included). This is what Ads Manager's "show existing reactions, comments and shares" does. Meta's native copy always publishes new posts. A creative belongs to one ad account, so `adSetId` must be in the source ad's account. 400 when the source ad has no creative yet.
+         */
+        reuseSourceCreative?: boolean;
     };
     headers?: {
         /**