Repository navigation
chore: refresh dependencies used to run and build Hermit - #67
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: 6b4620f2-ec4a-4601-9986-d34c3db110ad
|
🦞👀 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 Hermit’s runtime dependencies, build tools, shared Node.js pin, and pinned setup-node action. Example: GitHub CI selects the repository’s Node.js version.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open for landing: it provides a focused dependency refresh absent from main, with passing checks and no actionable findings. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherPackage manifests and lockfiles supply the Worker build and Bun gateway forwarder, which serve web requests and forward Discord events. flowchart LR
A[Dependency and Node pins] --> B[Bun installs]
B --> C[Worker build]
C --> D[Cloudflare Worker]
B --> E[Gateway forwarder]
F[Discord events] --> E
E --> D
Technical reviewBest possible solution: Land the focused refresh through the existing verified build and deployment workflow. Do we have a high-confidence way to reproduce the issue? This maintenance PR does not report a reproducible application bug. Is this the best way to solve the issue? Updating the existing pins and lockfiles is appropriately scoped and preserves the established security overrides and deployment ownership. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 67bc1f746e09. 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:24 PM ET / November 21, 2026, 03:24 UTC. |
What Problem This Solves
Hermit’s Worker and Discord gateway forwarder are pinned to older dependency and build-tool releases. This update brings those pins forward without adopting packages that have not cleared the seven-day maturity window.
User Impact
No user-visible change, migration, or action is expected. GitHub CI and Cloudflare Workers Builds will use the same updated Node.js 24 release. Merging can trigger the existing main-branch Cloudflare build; no deployment was dispatched.
Why This Change Was Made
Update the Worker’s Drizzle, React, routing, and CSS dependencies; align the forwarder’s Bun types with CI’s Bun; and update the WebSocket pin in both projects. Move the shared Node.js pin to the latest eligible 24.x security patch and keep the setup-node action pinned to the exact release commit. Carbon, Wrangler, and the incident-qualified
workerdoverride are unchanged.Evidence
git diff --checkalso passed.Direct pins and exact publication evidence
drizzle-ormreactreact-domreact-router@types/bun@types/nodetailwindcss@tailwindcss/postcssws(both locks)postcss949feb2413d6458794dcd2491c4babbbce0c15c1)The Node.js Linux artifact matched the upstream SHA-256 manifest. The upstream 24.22.3 source retains the same blocked certificate-key hashes as the existing 24.22.1 pin. The setup-node pin resolves to the exact GitHub release tag and retains
.node-versionsupport.Worked on by
Work sessions
Linked for team reference; these sessions aren’t public.