Repository navigation
chore: refresh dependencies used for Plugin Inspector checks - #159
roboclaw-bot wants to merge 2 commits into
Conversation
Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com>
Worked on by: - @vincentkoc Co-authored-by: vincentkoc <25068+vincentkoc@users.noreply.github.com> OpenClaw-Publication: 89aaf492-9ce0-464f-af77-d10914e83077
|
🦞👀 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. |
|
Codex review: needs maintainer review before merge. What this changesUpdates CI Node patches, Crabbox pnpm tooling and its pinned setup action, and the transitive ESTree declarations. Example: The Windows SDK workflow provisions Node before running its existing checks.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep open: this PR provides a focused dependency refresh that is absent from main, with passing checks on the reviewed head and no actionable defects found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherGitHub workflows provision tooling and install the locked dependency graph, then produce compatibility-test and memory-benchmark results. flowchart LR
A[Repository revision] --> B[GitHub workflows]
B --> C[Node and pnpm setup]
C --> D[Dependency installation]
D --> E[Tests and memory benchmarks]
E --> F[Check results]
Technical reviewBest possible solution: Land the focused refresh through the existing workflows while preserving package contracts and supported Node versions. Do we have a high-confidence way to reproduce the issue? This is maintenance rather than a bug report; the pinned diff directly establishes the older tooling selected on main. Is this the best way to solve the issue? Updating the existing version selections and lockfile entry is the smallest complete change, with no additional production machinery or tests needed. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against a1c224e468dc. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceWhat I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
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 Reviewed November 20, 2026, 10:22 PM ET / November 21, 2026, 03:22 UTC. |
What Problem This Solves
Plugin Inspector’s automated checks and Crabbox hydration still use older patch releases of Node and older pnpm tooling. The lockfile also has an older compatible release of the ESTree type declarations used by the scope analyzer.
User Impact
User impact: No user-visible change or action required. The supported Node versions, inspector package version, and release workflow are unchanged.
Why This Change Was Made
Use the latest eligible patches on the existing Node 22 and 24 lines in CI and hydration, update hydration’s pnpm and pin its setup action to the exact release commit, and refresh the transitive ESTree types. All updates satisfy the inclusive 2026-11-14 01:46 UTC cutoff. No new runtime dependencies are added.
Evidence
A credential-free, network-isolated install passed the 939-test suite, package-contents guard, and 12 retained-import probes on Node 22. The matching
npm installstep did not rewrite the lockfile. All 21 focused SDK and failure-diagnostics tests passed on Node 24; the verified pnpm Linux artifact ran and the changed workflow files parsed. Windows and the publish-memory benchmark are left to normal PR CI; hydration and release workflows were not dispatched.Version and age evidence
73e46992. The native bootstrap lock pins pnpm 12.17.0 and 14 platform artifacts. All 15 integrity values matched the registry; the artifacts were published 2026-10-30 between 14:22:58.005 and 14:23:51.302 UTC.Requested by @vincentkoc.
Work sessions
Linked for team reference; these sessions aren’t public.
Worked on by