Skip to content

fix(whatsapp): bump Baileys to v7.0.0-rc13 for LID group support (#43830) - #43934

Closed
kyssta-exe wants to merge 1 commit into
NousResearch:mainfrom
kyssta-exe:auto-fix/issue-43830
Closed

fix(whatsapp): bump Baileys to v7.0.0-rc13 for LID group support (#43830)#43934
kyssta-exe wants to merge 1 commit into
NousResearch:mainfrom
kyssta-exe:auto-fix/issue-43830

Conversation

@kyssta-exe

Copy link
Copy Markdown
Contributor

Fixes #43830. Bump Baileys from commit 01047de (v7.0.0-rc.9 era) to v7.0.0-rc13 (8053b08). The old pin silently failed to deliver outbound messages to WhatsApp groups fully migrated to LID addressing: sendMessage resolved successfully but messages never reached the group. v7.0.0-rc13 includes the LID addressing fix.

@kyssta-exe
kyssta-exe requested a review from a team June 11, 2026 02:45
@alt-glitch alt-glitch added type/bug Something isn't working P2 Medium — degraded but workaround exists comp/gateway Gateway runner, session dispatch, delivery platform/whatsapp WhatsApp Business adapter duplicate This issue or pull request already exists labels Jun 11, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

Duplicate of #43840 — both bump the WhatsApp bridge Baileys pin to v7.0.0-rc13 to fix silent outbound drops to fully-LID groups (#43830). #43840 is the earlier open PR.

@tonydwb tonydwb left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review Summary

Verdict: Approved

Fix: Bump Baileys to v7.0.0-rc13 for LID group support (#43830)

  • Trivial dependency pin update: changes the Baileys git commit ref to a newer hash.
  • Bumps from 01047de... to 8053b08... to pick up LID group support.
  • No code changes, no test impact.

Reviewed by Hermes Agent

@austinpickett

Copy link
Copy Markdown
Collaborator

Thanks for this — but it duplicates #43840, which pins the same Baileys commit (8053b086ecc97ec3f78299561de11959bab05d39) for the same LID group-send fix.

#43840 is the canonical PR here: it updates both package.json and package-lock.json, whereas this PR only bumps package.json and leaves the lockfile pinned to the old 01047deb commit — which would fail npm ci validation.

Closing in favor of #43840. If that PR stalls we can revisit, but the lockfile sync there makes it the complete fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/gateway Gateway runner, session dispatch, delivery duplicate This issue or pull request already exists P2 Medium — degraded but workaround exists platform/whatsapp WhatsApp Business adapter type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WhatsApp bridge: sends to LID-addressed groups silently dropped — bump Baileys pin to v7.0.0-rc13

4 participants