发布

  • v0.8.19

    frostbyte_neo 发布于 2026-07-17 08:56:58 +00:00 | 1783 次提交 在此版本后已推送到 main

    Closes out the whatsapp-web.js id-rename saga (WA Web 2.3000.x renamed
    MsgKey._serialized -> $1) across every remaining path: live inbound message
    mapping, message revocation, status listing and channel reads. The revocation
    fix matters even on a fully patched install — whatsapp-web.js overwrites the
    normalized id with a raw protocolMessageKey spread, so without the fallback a
    deleted message's text stayed in the database while WhatsApp showed it deleted.

    Also: the build-time backport can no longer latch a half-patched dependency;
    status posts fail honestly rather than fabricating a 201 with an invented
    timestamp; the dashboard's Message Tester reports real HTTP status codes instead
    of two hardcoded strings; typed SDK records match the payloads the server
    actually returns; and four dashboard fixes covering CSV export truncation, an
    overstated session count, a plain-HTTP CSP trap, and a guessed engine being
    persisted as a choice.

    A documentation pass removed eleven verified-false sentences, most importantly
    that status posting returns 501 on whatsapp-web.js (untrue since #714) while the
    recipients allow-list was promised but silently ignored on that engine.

    下载附件