From d25c5055a25a27ce768c7d412211904aabf311e3 Mon Sep 17 00:00:00 2001 From: Renato Alcara Date: Fri, 1 May 2026 22:53:29 -0300 Subject: [PATCH] chore: bump WhatsApp Web version to v2.3000.1038585534 on Mar/18 base Restoring master to commit d04a3e1af8 ("fix: restore working carousel send/render path (#297)") which is the LAST KNOWN GOOD state before the inbound latency regression. PR #303 (pastParticipants HistorySync LID) and subsequent commits introduced the per-message LID/PN session drift that locked the inbound pipeline behind Bad MAC retry storms in production. WHAT IS PRESERVED: - Tag `archive/master-pre-restore-2026-05-01` points at the previous master tip (d03b625a89, "chore: update WhatsApp Web version (#404)") - Branch `master-archive-pre-restore-2026-05-01` mirrors that tip for easy browsing - All 137 commits between Mar/18 and the previous master tip remain in git history; downstream forks lose nothing WHAT IS LOST FROM MASTER (preserved in archive): - View-once features (#310, #316, #322, #355) - USync username inbound (#382) - Early-ignore JIDs (#383) - History sync memory/CPU optimisation (#385) - tcToken full lifecycle (#386, #387) - Async LID mapping restore (#390) - Decrypt-error noise reduction (#391) - Detach post-upsert work (#392) - Bounded-retry replacing CircuitBreaker (#393) - wire address lock (#396) - Decryption fail-fast (#402) - ~30 WhatsApp Web/proto version updates (only the latest is reapplied) Re-add features one at a time on top of this base, testing each so the inbound regression doesn't silently sneak back in. Co-Authored-By: Claude Opus 4.7 (1M context) --- src/Defaults/baileys-version.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Defaults/baileys-version.json b/src/Defaults/baileys-version.json index ff7af088..f5ca7043 100644 --- a/src/Defaults/baileys-version.json +++ b/src/Defaults/baileys-version.json @@ -1 +1 @@ -{"version":[2,3000,1035406580]} +{"version":[2,3000,1038585534]}