Shipped · APIs and backends

What wppconnect-team/wppconnect shipped

The public repository of Wppconnect · github.com/wppconnect-team/wppconnect

Written by FoxPlug from the repository's own releases; not affiliated with Wppconnect. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/wppconnect-team/wppconnect; Wppconnect did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for wppconnect, free

Week of October 19, 2026

What shipped

Why it matters

This week fixes several session lifecycle problems that users could hit in production: false connected states on the QR screen, early auto-close of restored sessions, and leaked Chromium processes. It also removes permanent idle polling and applies the default browser arguments that were previously ignored. Chat unread actions now depend on a newer wa-js version to match current WhatsApp Web behavior.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

2.3.6 is out. Unpaired QR sessions no longer report as connected, restored sessions are no longer auto-closed right away, and the browser process tree is released on close. Idle polling timers are gone and default launch args now apply.

Post for LinkedIn

Version 2.3.6 is released. This week focuses on session stability and resource use. Unpaired QR sessions no longer report Connected or inChat, restored sessions are marked logged before waiting for chat so they are not auto-closed, and disconnectedMobile is only reported after a real unpair. The browser process tree is now released on close and on failed create, and the browser auto-closes when only blank or closed tabs remain. Permanent idle polling timers were removed, default launch args now apply so the curated chromiumArgs list is used, and media helpers bound their file and download reads. Unread chat actions now require wa-js 4.7.2 to stay correct on newer WhatsApp Web builds.

Week of October 12, 2026

What shipped

Why it matters

Group member fetches no longer make one page round-trip per member, and media decryption no longer builds multi-MB intermediate strings on the event loop. The release also makes create() survive slow WPP.isReady exposure and makes close() stop pending QR checks. Users on 2.3.x get a set of auth, browser and dependency fixes in v2.3.5.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V2.3.5 is out. getGroupMembers now resolves member contacts in one page call instead of one per member, media decrypt works on raw buffers, QR attempts are cancelled on close, and create() tolerates slow WPP.isReady. wa-js bumped to 4.7.1.

Post for LinkedIn

Wppconnect v2.3.5 is out. This week the group member lookup was reworked: getGroupMembers now fetches participant contacts in a single page call instead of calling getContact once per member, which removes the N+1 page round-trips for large groups. Media decryption now feeds raw buffers directly instead of converting through hex strings and per-byte loops on the event loop. Auth fixes cancel pending QR attempts before close() awaits page shutdown, browser injection tolerates WhatsApp Web taking more than 30s to expose WPP.isReady, and page bindings are guarded against double registration on reused pages. The release also bumps @wppconnect/wa-js to 4.7.1.

More from wppconnect-team/wppconnect on GitHub

Merged pull requests

Releases

From the changelog

From the README

Who ships it

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-28.

Is this your repo? Ask us to remove this page.