@whanext/core 0.19.8 → 0.19.9

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.19.9
+
+- Fixed live `message_addon` edits being discarded when Zapo reports the parent message timestamp instead of the mutation timestamp.
+- Serialized decrypted edit addons through the same protocol-mutation queue used by `message_protocol`, preserving edit/revoke ordering.
+- Offline-resume edit addons remain ignored by default unless `processOfflineMessages` is enabled.
+
 ## 0.19.8
 
 ### Fixed

package/dist/index.js

@@ -3199,9 +3199,18 @@ var ZapoProvider = class {
       ...protocolKey?.participant !== void 0 ? { participant: protocolKey.participant } : event.key.participant !== void 0 ? { participant: event.key.participant } : {},
       ...protocolKey?.participantAlt !== void 0 ? { participantAlt: protocolKey.participantAlt } : event.key.participantAlt !== void 0 ? { participantAlt: event.key.participantAlt } : {}
     };
-    void this.#handleProtocolEvent({
+    if (event.offline === true && this.#options.processOfflineMessages !== true) {
+      this.#logger.debug("Ignored offline Zapo edit addon from before the current live connection.", {
+        messageId: event.key.id ?? void 0,
+        targetMessageId,
+        chatId: target.remoteJid ?? event.key.remoteJid ?? void 0
+      });
+      return;
+    }
+    const mutationTimestampSeconds = toSeconds(protocol?.timestampMs) ?? (event.offline === true ? toSeconds(event.timestampSeconds) : void 0) ?? Math.floor(Date.now() / 1e3);
+    this.#enqueueProtocolEvent({
       key: event.key,
-      ...event.timestampSeconds !== void 0 ? { timestampSeconds: event.timestampSeconds } : {},
+      timestampSeconds: mutationTimestampSeconds,
       protocolMessage: {
         type: proto.Message.ProtocolMessage.Type.MESSAGE_EDIT,
         key: target,