@getlatedev/node 0.2.1447 → 0.2.1448

package/dist/index.d.mts

@@ -22077,9 +22077,18 @@ type event52 = 'review.restored';
 /**
  * Webhook payload for the review.updated event. Same shape as review.new.
  *
- * Fired when the reviewer edits their text or rating, or when a reply is posted through POST /v1/inbox/reviews/{reviewId}/reply.
+ * Fired when the reviewer edits their text or rating, or when a reply is added, edited or removed.
  *
- * A reply written directly in Google's own interface does NOT fire it: Google emits no notification when a reviewReply is written.
+ * A reply posted through POST /v1/inbox/reviews/{reviewId}/reply fires immediately. The periodic check then reports it again with the full review payload, so expect a second delivery.
+ *
+ *
+ * Replies written or removed in Google's own interface, and replies removed through the API, are reported by the periodic check.
+ *
+ *
+ * For replies written in Google, that is usually within 6 hours for reviews updated in the last 30 days, and usually within about 7 days for older ones.
+ *
+ *
+ * Only teams with a webhook subscribed to review.updated are checked. A removed reply fires with hasReply false.
  *
  * When a reply is present, review.hasReply is true and review.reply is populated.
  *

package/dist/index.d.ts

@@ -22077,9 +22077,18 @@ type event52 = 'review.restored';
 /**
  * Webhook payload for the review.updated event. Same shape as review.new.
  *
- * Fired when the reviewer edits their text or rating, or when a reply is posted through POST /v1/inbox/reviews/{reviewId}/reply.
+ * Fired when the reviewer edits their text or rating, or when a reply is added, edited or removed.
  *
- * A reply written directly in Google's own interface does NOT fire it: Google emits no notification when a reviewReply is written.
+ * A reply posted through POST /v1/inbox/reviews/{reviewId}/reply fires immediately. The periodic check then reports it again with the full review payload, so expect a second delivery.
+ *
+ *
+ * Replies written or removed in Google's own interface, and replies removed through the API, are reported by the periodic check.
+ *
+ *
+ * For replies written in Google, that is usually within 6 hours for reviews updated in the last 30 days, and usually within about 7 days for older ones.
+ *
+ *
+ * Only teams with a webhook subscribed to review.updated are checked. A removed reply fires with hasReply false.
  *
  * When a reply is present, review.hasReply is true and review.reply is populated.
  *

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -20665,9 +20665,18 @@ export type event52 = 'review.restored';
 /**
  * Webhook payload for the review.updated event. Same shape as review.new.
  *
- * Fired when the reviewer edits their text or rating, or when a reply is posted through POST /v1/inbox/reviews/{reviewId}/reply.
+ * Fired when the reviewer edits their text or rating, or when a reply is added, edited or removed.
  *
- * A reply written directly in Google's own interface does NOT fire it: Google emits no notification when a reviewReply is written.
+ * A reply posted through POST /v1/inbox/reviews/{reviewId}/reply fires immediately. The periodic check then reports it again with the full review payload, so expect a second delivery.
+ *
+ *
+ * Replies written or removed in Google's own interface, and replies removed through the API, are reported by the periodic check.
+ *
+ *
+ * For replies written in Google, that is usually within 6 hours for reviews updated in the last 30 days, and usually within about 7 days for older ones.
+ *
+ *
+ * Only teams with a webhook subscribed to review.updated are checked. A removed reply fires with hasReply false.
  *
  * When a reply is present, review.hasReply is true and review.reply is populated.
  *