Skip to content

fix(parity): wa lacks the sync-first options a pushed-history messenger is not offered - #1428

Merged
leemour merged 1 commit into
mainfrom
fix/wa-parity-pushed-history
Oct 17, 2026
Merged

leemour merged 1 commit into
mainfrom
fix/wa-parity-pushed-history

Conversation

@leemour

@leemour leemour commented Oct 17, 2026

Copy link
Copy Markdown
Collaborator

Task

Unblock the 0.316.0 release: its Parity job failed on whatsapp-cli (run 39022464895).

Why

0.315.0 (#1423) stopped offering --sync-first, --sync-time, --max-chats and --max-messages to a messenger with history: "store". #1424 placed wa's column from a wa build that predates 0.315.0, so 20 options said all that wa no longer has.

What

Those 20 options are now in: [max, tg], with the reason that a pushed-history messenger has nothing to sync first. The option catalogue is re-rendered, and the changelog has a line under Unreleased.

Testing

wa main (0f17395) was built against this branch's packed tarball: cli-core-parity wa reports 0 differences and --pages passes. manifestProblems reports 0. The parity and steps tests pass.


Reviewed against the review checklist — §B for code.

🤖 Generated with Claude Code

…er is not offered

0.315.0 stopped offering --sync-first, --sync-time, --max-chats and --max-messages to a messenger
with history: "store"; wa's column was placed from a build before that, so the 0.316.0 release's
Parity job failed on wa.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour merged commit c9408a1 into main Oct 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant