chore(deps): bump @tencent-weixin/openclaw-weixin from 2.4.6 to 2.4.9 in /plugins/openclaw-weixin

[dependabot]

Bumps @tencent-weixin/openclaw-weixin from 2.4.6 to 2.4.9.

Maintainer changes

This version was pushed to npm by zengyi1001, a new releaser for @​tencent-weixin/openclaw-weixin since your current version.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: blocked before merge. Reviewed September 21, 2026, 5:52 AM ET / 09:52 UTC (Revision 2).

ClawSweeper review

What this changes

Updates Crabpot’s Weixin compatibility fixture from 2.4.6 to 2.4.9, expands its dependency lockfile, and refreshes generated compatibility reports.

Merge readiness

⛔ Blocked before merge - 3 items remain

The update remains useful and is not implemented on main. The earlier lockfile finding remains unresolved after the report refresh.

Priority: P2
Reviewed head: 59e656467e7d5b3f47aa636c9ae06b2588abca04

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The useful version update and refreshed reports retain one concrete, mechanically repairable lockfile defect.
Proof confidence	🌊 off-meta tidepool	Not applicable: This Dependabot-authored fixture update is exempt from contributor runtime proof; generated compatibility profiles are supplemental and do not resolve the lockfile finding.
Patch quality	🦐 gold shrimp (3/6)	1 actionable review finding remain.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This Dependabot-authored fixture update is exempt from contributor runtime proof; generated compatibility profiles are supplemental and do not resolve the lockfile finding.
Evidence reviewed	11 items	Applicable repository policy: Read the full root AGENTS.md. No nested AGENTS.md files or maintainer-notes directory were found. The host-linked dependency rule applies directly to the introduced OpenClaw peer graph. Update remains necessary: The pinned main lock contains Weixin 2.4.6. GitHub confirmed the current PR remains open and unmerged at the reviewed head; the latest release, v0.2.1, also pins 2.4.6. Release check: The latest published release is v0.2.1; its fixture manifest retains Weixin 2.4.6.
Findings	1 actionable finding	[P2] [P2] Exclude the workspace-owned host from the fixture lock
Security	None	None.

How this fits together

Crabpot checks plugin fixtures against a separately supplied OpenClaw host. Fixture package locks feed dependency audits, while compatibility checks produce reports and dashboard summaries.

flowchart LR
  A[Weixin package pin] --> B[Fixture dependency lock]
  B --> C[Fixture security audit]
  A --> D[Compatibility checks]
  E[Workspace OpenClaw host] --> D
  C --> F[CI result]
  D --> G[Reports and dashboard]

Loading

Before merge

• [P2] Exclude the workspace-owned host from the fixture lock (P2) - This entry brings OpenClaw 2026.9.4 and 358 other peer packages into a fixture lock that previously contained only the plugin and its two dependencies. scripts/check-fixture-security.mjs audits this entire lock, so unrelated host advisories can now block fixture CI even though the workspace supplies OpenClaw separately. This remains unchanged since the previous review and contradicts the supported refresh procedure in plugins/README.md:199–202. Regenerate with --package-lock-only --ignore-scripts --legacy-peer-deps, retaining 2.4.9 and the existing overrides.
• Resolve merge risk (P1) - The fixture lock includes the separately managed OpenClaw host graph, allowing unrelated host dependency advisories to block fixture CI.
• Complete next step (P2) - Regenerate the Weixin lock without automatic host peers, retaining 2.4.9 and existing overrides, then verify fixture security and compatibility checks.

Findings

• [P2] [P2] Exclude the workspace-owned host from the fixture lock — plugins/openclaw-weixin/package-lock.json:3491-3497

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Fixture lock expansion	3 to 362 dependency entries; 359 added peer packages	The added entries belong to the separately supplied host and unnecessarily broaden fixture auditing.

Merge-risk options

Maintainer options:

1. Restore the plugin-only lock (recommended)
   Regenerate the fixture lock with legacy peer resolution and verify security and compatibility checks while preserving the new version and overrides.

Copy recommended automerge instruction

@clawsweeper automerge

Special instructions:
Regenerate plugins/openclaw-weixin/package-lock.json with --package-lock-only --ignore-scripts --legacy-peer-deps, preserving Weixin 2.4.9 and all existing overrides; verify the OpenClaw peer graph is absent and run fixture security and compatibility checks.

Technical review

Best possible solution:

Keep the 2.4.9 fixture update with a minimal plugin dependency lock, preserved security overrides, and compatibility reports validated against the workspace host.

Do we have a high-confidence way to reproduce the issue?

Yes, by source inspection: the branch adds 359 peer entries, and the checker audits the entire lock without excluding host peers. No audit or artifact-producing tests were executed during this read-only review.

Is this the best way to solve the issue?

The version bump is appropriate, but its lockfile generation is not: the documented legacy-peer-deps path preserves the existing host boundary without changing audit policy.

Full review comments:

• [P2] [P2] Exclude the workspace-owned host from the fixture lock — plugins/openclaw-weixin/package-lock.json:3491-3497
  This entry brings OpenClaw 2026.9.4 and 358 other peer packages into a fixture lock that previously contained only the plugin and its two dependencies. scripts/check-fixture-security.mjs audits this entire lock, so unrelated host advisories can now block fixture CI even though the workspace supplies OpenClaw separately. This remains unchanged since the previous review and contradicts the supported refresh procedure in plugins/README.md:199–202. Regenerate with --package-lock-only --ignore-scripts --legacy-peer-deps, retaining 2.4.9 and the existing overrides.
  Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.98

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against d43a6c9e875c.

Labels

Label justifications:

• P2: This is a bounded dependency maintenance update with a concrete fixture-lock repair.
• merge-risk: 🚨 automation: The introduced host graph expands the fixture security gate’s audit scope to unrelated host dependencies.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This Dependabot-authored fixture update is exempt from contributor runtime proof; generated compatibility profiles are supplemental and do not resolve the lockfile finding.

Evidence

Acceptance criteria:

• [P1] npm run check:fixture-security.
• [P1] node scripts/sync-fixtures.mjs --check.
• [P1] node scripts/inspect-fixtures.mjs --check.
• [P1] npm run check.

What I checked:

• Applicable repository policy: Read the full root AGENTS.md. No nested AGENTS.md files or maintainer-notes directory were found. The host-linked dependency rule applies directly to the introduced OpenClaw peer graph. (AGENTS.md:11, 59e656467e7d)
• Update remains necessary: The pinned main lock contains Weixin 2.4.6. GitHub confirmed the current PR remains open and unmerged at the reviewed head; the latest release, v0.2.1, also pins 2.4.6. (plugins/openclaw-weixin/package-lock.json:15, d43a6c9e875c)
• Release check: The latest published release is v0.2.1; its fixture manifest retains Weixin 2.4.6. (plugins/openclaw-weixin/package.json:7, 1e7e129eaf06)
• Unresolved prior finding: The previous review requested removal of the workspace-owned host graph. Comparing its reviewed head with the current head produces no changes under the Weixin fixture, so that finding and rank-up move remain unresolved. (plugins/openclaw-weixin/package-lock.json:3491, 59e656467e7d)
• Introduced dependency expansion: Read-only JSON comparison found 4 lock entries before and 363 after, including the root entry. All 359 additions carry peer:true, including OpenClaw 2026.9.4. The plugin still declares only qrcode-terminal and zod as direct dependencies. (plugins/openclaw-weixin/package-lock.json:3491, 59e656467e7d)
• Concrete audit consequence: The fixture security checker audits each complete committed lock with --omit=dev and does not exclude host peer packages. Lock-refreshable high or critical findings in the added host graph therefore become fixture failures. (scripts/check-fixture-security.mjs:35, 59e656467e7d)

Likely related people:

• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; confidence: low)
• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Remove the host peer graph while preserving 2.4.9 and overrides, then verify fixture security and compatibility checks.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)

• reviewed 2026-09-21T09:37:10.126Z sha 5a8f093 :: blocked before merge. :: [P2] [P2] Exclude the workspace-owned host from the fixture lock