Conversation
litang9
marked this pull request as ready for review
August 7, 2026 16:11
8 tasks
|
Thanks for addressing the changing OpenClaw channel SDK surface. The community-maintained distribution independently adopted the stable public The community port targets its declared OpenClaw >=2026.6.1 boundary and verifies the real minimum and development host profiles, so it does not need to copy a dynamic fallback for private or removed entry points. This is a community release status update, not a claim that this Tencent PR has been merged upstream: |
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
2 participants
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
createTypingCallbacksfrom the canonicalopenclaw/plugin-sdk/channel-outboundentrypointchannel-runtimeentrypoint only when an older supported host does not exportchannel-outboundWhy
OpenClaw removed
openclaw/plugin-sdk/channel-runtimein2026.7.2-beta.4. As a result,@tencent-weixin/openclaw-weixin@2.4.6cannot start on current beta hosts, including2026.7.2-beta.7.A direct import replacement would fix current hosts but break the plugin's existing
openclaw >=2026.5.12compatibility contract because those older hosts do not exportchannel-outbound. The narrow resolver uses the canonical entrypoint first and retains the old entrypoint only for that declared compatibility range.Related: openclaw/openclaw#115478
Validation
npm run typecheckwithopenclaw@2026.5.12npm run buildwithopenclaw@2026.5.12openclaw@2026.5.12andopenclaw@2026.7.2-beta.7installsopenclaw plugins installon2026.7.2-beta.7; after a gateway restart, the Weixin long-poll account reportsrunning=true,reconnectAttempts=0, andlastError=nullnpm teststill exits nonzero on the repository's existing global branch coverage threshold: observed 89.14%, required 90%. The new resolver itself is fully covered except for the non-Error guard branch.