Repository navigation
chore(deps): bump @tencent-weixin/openclaw-weixin from 2.4.9 to 2.4.10 in /plugins/openclaw-weixin - #475
Conversation
Bumps @tencent-weixin/openclaw-weixin from 2.4.9 to 2.4.10. --- updated-dependencies: - dependency-name: "@tencent-weixin/openclaw-weixin" dependency-version: 2.4.10 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
…rn/plugins/openclaw-weixin/tencent-weixin/openclaw-weixin-2.4.10
|
Codex review: needs real behavior proof before merge. What this changesThis PR updates the Weixin fallback to 2.4.10, refreshes Zod to 4.6.5, and adds an Unreleased credit. Example: Crabpot uses the committed Weixin fallback package.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness⛔ Blocked before merge - 3 items remain This PR remains useful and is not implemented on main; the repaired lock is sound, and the member-approved manual landing path resolves the earlier changelog finding. Priority: P2 Before merge
Findings
Tests
Agent review detailsHow this fits togetherCrabpot materializes configured plugin artifacts into isolated workspaces with a separately supplied OpenClaw host, then produces compatibility captures and reports. flowchart LR
A[Fixture configuration] --> B[Npm artifact selection]
B --> C[Weixin package]
C --> D[Isolated workspace]
E[Frozen OpenClaw host] --> D
D --> F[Compatibility captures]
F --> G[Reports]
Technical reviewBest possible solution: Retain the repaired fallback update and approved changelog, then establish authorization enforcement through the real downstream effect owners. Do we have a high-confidence way to reproduce the issue? This is a dependency refresh rather than a reproduced Crabpot bug; source inspection confirms the package changes, and qualification reports admission checks without demonstrating a new authorization failure. Is this the best way to solve the issue? Updating the existing fixture pin and minimal lock preserves the established acquisition and host boundaries without adding a competing implementation. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against d300f1bf92fb. Merge-risk optionsMaintainer options:
Provenance checked
TestingProof path: in-process harness. SecurityNeeds attention: No introduced bypass was established, but the changed authorization handoff still needs final-effect validation. EvidenceSecurity concerns:
What I checked:
Likely related people:
LabelsLabel changes:
Label justifications:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment HistoryReview history (2 earlier review cycles)
Reviewed October 14, 2026, 11:05 PM ET / October 15, 2026, 03:05 UTC (Revision 3). |
|
Updated this PR’s original Dependabot branch to Qualification: run 38611002012 passed against frozen host Both workspace audits returned raw exit 1: 8 advisories (3 critical, 3 high, 2 moderate) outside the repaired four-entry fixture lock. Both plugin versions declare identical development/workspace dependencies. The artifact omits the installed lock, so it does not establish exact installed-host resolution or audit the frozen host’s dependency graph. These warnings and the existing policy remain unchanged. The temporary CI branch was deleted and its absence verified. Independent source/lock review and the scoped metadata autoreview found no actionable issue; normal PR CI and fresh exact-head ClawSweeper review are still required. |
|
@clawsweeper re-review |
|
🦞👀 Re-review progress:
|
|
Holding this update at Four isolated qualification attempts stopped before any of the 24 planned old/new admission cases or config-preservation checks ran. These are test-environment failures, not demonstrated plugin regressions or passing runtime proof. Existing mock-SDK qualification remains 0 passed / 0 failed / 2 blocked. Source review identifies inherited limits: local transport commands and media handling precede admission, and in-flight messages retain their earlier allowlist snapshot in both versions. These are not new regressions. Native proof must distinguish plugin admission from full Gateway command execution. Unblock: demonstrate allowed, forbidden, cross-account, revoked-before-call and ownerless behavior through the real registered SDK, plus preservation of existing config/account/pairing data during reload; then obtain fresh required CI on the strict current base and an exact-head ClawSweeper review. Audit warnings remain: eight findings outside the four-entry fixture lock; the captured installed workspace graph was insufficient to attribute them precisely. No releases performed. All four temporary qualification leases were released. |
|
Qualification update for Actual published 2.4.9 and 2.4.10 message processors were exercised with the registered source SDK at frozen OpenClaw This proves plugin admission and recorded handoff, not full Gateway or live Weixin behavior: terminal dispatch/session recording and outbound fetch were substituted; no host-principal, downstream command execution, media, or live typing claim is made. In-flight authorization snapshots and pre-authorization local commands remain inherited behavior in both versions; The run's outer status remains 1: its receipt parser missed ANSI-prefixed JSON. Independently checking the immutable capture after ANSI-only normalization recovered all 24 unique cases and the config receipt, without rerunning or changing assertions. The isolated unit and lease were released. The earlier eight raw workspace audit advisories remain recorded outside the four-entry fixture lock. Both versions declare identical development dependencies; the installed host graph was not captured, so no exact host-resolution or zero-security claim is made. Metadata autoreview is clean. The meaningful changelog remains; its optional Dependabot auto-merge allowlist failure does not replace required checks. Fresh required CI and exact-head ClawSweeper review remain necessary before landing. @clawsweeper re-review |
|
🦞👀 Re-review progress:
|
Patch smol-toml, OpenTelemetry core, and qs in the Codex and TencentDB fixture locks while retaining qualified plugin versions. Accept only Node's exact optional TypeScript warning before TencentDB's known missing-module diagnostic, keeping unrelated failures strict and the captured fixture LF-stable on Windows. Fold in the qualified Weixin 2.4.10 and Zod 4.6.5 update from #475, retaining its four-entry fixture lock without installing OpenClaw host peers. Preserve the native admission/config proof limitations documented there. Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Patch smol-toml, OpenTelemetry core, and qs in the Codex and TencentDB fixture locks while retaining qualified plugin versions. Accept only Node's exact optional TypeScript warning before TencentDB's known missing-module diagnostic, keeping unrelated failures strict and the captured fixture LF-stable on Windows. Fold in the qualified Weixin 2.4.10 and Zod 4.6.5 update from #475, retaining its four-entry fixture lock without installing OpenClaw host peers. Preserve the native admission/config proof limitations documented there. Co-authored-by: Vincent Koc <vincentkoc@ieee.org> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
Consolidated into #503 with Weixin 2.4.10, Zod 4.6.5, and the four-entry lock that keeps OpenClaw host peers out of the fixture graph. Vincent's and Dependabot's contributions are credited in the changelog and commit. The prior native admission/config proof and its limits remain linked from #503. The combined change received a fresh independent P0–P2 review and passed the protected current-main merge gate; this does not broaden the recorded proof into live Gateway, downstream command, media, or provider compatibility. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @tencent-weixin/openclaw-weixin from 2.4.9 to 2.4.10.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)