[jlucaso1]

Update all 11 whatsapp-rust packages together from 1fcb58a272334604261eb23f5e2a3f1b54059a33 to the confirmed main head af2e018c270f03c8733d303e8c56093f8e720952. Rechecked upstream immediately before publication and again after local validation.

The upstream range includes offline receive batch handling, inbound voice playout limits, contextual IQ/group notification contracts, retry conformance tests, and allocation changes in history/cache paths. No measured performance claims. No client API changes were needed.

Only the root Cargo.lock references this Git source. Keep the shared branch = "main" declarations. Upstream SQLite storage requires scheduled-thread-pool =0.2.7, removing unused parking_lot 0.13, parking_lot_core 0.10, lock_api 0.5 and redox_syscall 0.9. Unrelated dependency versions and resolution edges are preserved. Based on client main fa54978, which already includes #285 and #286.

Validation on head d09e8b7ae5babe2b11504e73732809c5f26c54d2:

• cargo fmt --all -- --check and git diff --check passed.
• cargo clippy --workspace --all-targets --all-features --locked -- -D warnings passed, including daemon, GUI and CLI.
• cargo test --workspace --all-features --locked passed: 2,402 tests/doctests, 0 failures, 37 ignored.
• Nightly 2026-10-29 GUI/session WASM check passed with the production shared-memory flags and -Z build-std=std,panic_abort. Existing WASM warnings remain.
• xtask fmt, Clippy and 50 tests passed.
• Both example plugins passed host fmt, Clippy and tests, 6 + 3 tests.
• Python memory driver tests: 4 passed. JavaScript benchmark/metadata/service-worker tests: 25 passed.
• Codex review completed with no findings on this exact head.

CI is queued, not passed. Windows/macOS, MSRV, browser runtime tests and release artifact builds remain unverified remotely. No local browser runtime run: matching chromedriver and wasm-bindgen-test-runner are not installed. Plugin wasm build/ignored integration coverage and CLI release-size budget remain for CI. The PR was merged externally at 2026-10-30 02:13:38 UTC while local validation was finishing. Verified main commit 33108ce14d3c02aaecf515957600ee22a90f06c7 contains all 11 core crates at the new revision. This task did not perform a merge or deployment. Remote CI remains pending.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[jlucaso1]

@codex review

Please review the whatsapp-rust lockfile update for source coherence, compatibility and unintended dependency changes. All 11 core crates must resolve to af2e018c270f03c8733d303e8c56093f8e720952; scheduled-thread-pool 0.2.7 is required by upstream.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-30T02:16:15.201526Z	d09e8b7	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: d09e8b7ae5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".