Skip to content

chore(chat-flow,faq-bot,after-hours): record 0.12.1 as the tested host - #58

Merged
rmyndharis merged 1 commit into
mainfrom
release/tested-0.12.1-trio
Aug 1, 2026
Merged

chore(chat-flow,faq-bot,after-hours): record 0.12.1 as the tested host#58
rmyndharis merged 1 commit into
mainfrom
release/tested-0.12.1-trio

Conversation

@rmyndharis

Copy link
Copy Markdown
Owner

Three plugins move testedOpenWAVersion from 0.8.1 to 0.12.1, each with a patch bump. No behaviour changed; the field is defined as the newest host the plugin was actually smoke-tested against, and that smoke has now been run.

All three were installed at these versions on a live OpenWA 0.12.1 host with a connected WhatsApp session, all enabled at the same time alongside two other responder plugins, and driven by real messages from a second connected number. Each answered exactly the messages meant for it, and every message was answered by exactly one plugin:

  • a message matching a faq-bot keyword rule was answered by faq-bot alone;
  • a message matching chat-flow's trigger started its menu flow, answered by chat-flow alone, and chat-flow then continued to own the contact's replies while they were inside the menu;
  • a message matching nothing specific fell through to the catch-all responder;
  • with that catch-all disabled, after-hours answered the same kind of message with its away message.

Before this ordering existed, each of those messages would have drawn a reply from all three.

Not covered, and stated as such in each changelog: group chats, media, and behaviour under load.

All three were installed together on a live OpenWA 0.12.1 host with a connected
WhatsApp session, alongside two other responder plugins, and driven by real
messages from a second connected WhatsApp number. Each answered exactly the
messages meant for it and nothing else: faq-bot on a matching keyword rule,
chat-flow on its trigger word (owning the contact's replies until the flow was
cleared), and after-hours with its away message once the other catch-all
responder was disabled.

No behaviour changed; each CHANGELOG records what the smoke test covered.
@rmyndharis
rmyndharis merged commit 56bd437 into main Aug 1, 2026
1 check passed
@rmyndharis
rmyndharis deleted the release/tested-0.12.1-trio branch August 1, 2026 06:42
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