Support current LINQ webhooks and Hermes adapter lifecycle - #2
Open
SYMBaiEX wants to merge 2 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the Hermes Linq plugin to accept both legacy and current LINQ message.received webhook payload shapes by normalizing current payloads into the adapter’s existing internal contract, while also aligning the adapter lifecycle with Hermes’ current connect(is_reconnect=...) calling convention.
Changes:
- Added
signing.normalize_message_received_data()to map current LINQ webhook payloads into the legacy-shaped contract used by the adapter. - Updated
LinqAdapterto call the normalizer, preserve the original payload onMessageEvent.raw_message, and accept keyword-onlyis_reconnectinconnect. - Extended unit tests and README documentation to cover both webhook versions and current group detection via
chat.is_group.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
tests/test_signing.py |
Adds coverage for normalizing current vs. legacy message.received payloads, including group flag and optional owner handling. |
signing.py |
Introduces payload normalization for current LINQ webhook shapes and updates group-chat classification docs. |
adapter.py |
Uses normalization for inbound webhooks, preserves raw payload on events, and updates connect signature for Hermes lifecycle compatibility. |
README.md |
Documents support for both legacy/current webhook payload versions and updated group detection notes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
SYMBaiEX
force-pushed
the
sym/current-webhook-compatibility
branch
from
August 7, 2026 02:22
3c9b090 to
2e1cd3c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
2026-02-03message.receivedpayloads while preserving legacy2025-01-01compatibilityMessageEvent.raw_messageis_reconnectconnection argumentCurrent LINQ webhooks place message fields such as
idandpartsdirectly underdata, while the older payload nested them underdata.message. Without normalization, the adapter rejects current inbound messages as missingmessage.id. Current Hermes also calls platform adapters withconnect(is_reconnect=...).The scope is intentionally limited to inbound webhook and Hermes lifecycle compatibility. It does not change outbound messaging, media handling, authentication, CLI behavior, or plugin registration.
Testing
python -m unittest discover -s tests -v— 28 tests passedpython -m py_compile adapter.py signing.py tests/test_signing.pygit diff --check upstream/main...HEADLinqAdapterremains concrete and matches the Hermes v2026.8.3BasePlatformAdapter.connectcontract