@getlatedev/node 0.2.1337 → 0.2.1338

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1337",
+  version: "0.2.1338",
   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: "@getlatedev/node",
-  version: "0.2.1337",
+  version: "0.2.1338",
   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": "@getlatedev/node",
-  "version": "0.2.1337",
+  "version": "0.2.1338",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -10638,7 +10638,10 @@ export const createAdCampaign = <ThrowOnError extends boolean = false>(options:
  *
  * **Live read, then write.** The campaign's switch is read from the platform first. When that
  * live read shows it already in the requested state nothing is written (`updated: 0`,
- * `skipped: 1`, with the reason). Otherwise the switch is written (`updated: 1`), read back and
+ * `skipped: 1`, with the reason), and when the campaign delivers in that state but some of its
+ * ads are stored in the other state (for example ads switched on in the platform's own UI and
+ * still stored `paused`), those ads (up to 20, at most once every 10 minutes per campaign) are
+ * re-read and stored. Otherwise the switch is written (`updated: 1`), read back and
  * stored, and the delivery status of the ads under it (up to 20) is re-read and stored, so an
  * immediate GET returns what the platform now reports. A stored switch never skips a write, and
  * when the platform cannot be read the write always goes out. On Meta the check reads the
@@ -11332,7 +11335,10 @@ export const deleteAdSet = <ThrowOnError extends boolean = false>(options: Optio
  *
  * **Live read, then write.** The ad set's switch is read from the platform
  * first. When that live read shows it already in the requested state
- * nothing is written (`updated: 0`, `skipped: 1`, with the reason).
+ * nothing is written (`updated: 0`, `skipped: 1`, with the reason), and
+ * when the ad set delivers in that state but some of its ads are stored in
+ * the other state, those ads (up to 20, at most once every 10 minutes per
+ * ad set) are re-read and stored.
  * Otherwise the switch is written (`updated: 1`), read back and stored, and
  * the delivery status of its ads (up to 20) is re-read and stored, so an
  * immediate GET returns what the platform now reports. A stored switch