Repository navigation
build(deps): refresh tracking worker and CI tooling - #1344
roboclaw-bot wants to merge 2 commits into
Conversation
Update worker overrides and the pinned Node, pnpm, and Dockerfile frontend versions. Preserve the worker release policy, inherited fresh pins, and Go build baselines. 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: 0f9fbfe5-4dde-4813-9e0f-de4c7640cf4a
|
🦞👀 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 changesThis PR refreshes tracking-worker dependencies, Node and pnpm pins, setup-node, and the Dockerfile frontend. Example: CI installs and builds the tracking worker.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open for landing: it contains useful dependency updates absent from main, all checks on the reviewed head pass, and no actionable introduced defect was found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherGitHub workflows consume pinned tools and the worker lockfile to validate the tracking worker and publish documentation; the Dockerfile frontend interprets the existing CLI image build. flowchart TD
A[Pull request source] --> B[GitHub workflows]
B --> C[Pinned Node and pnpm]
C --> D[Worker frozen installation]
D --> E[Worker validation]
B --> F[Documentation build]
A --> G[Dockerfile frontend]
G --> H[CLI image build]
Technical reviewBest possible solution: Land the focused pin refresh with the existing package-manager, release-age, and security policies preserved. Do we have a high-confidence way to reproduce the issue? This maintenance PR does not report a behavioral bug requiring reproduction. Is this the best way to solve the issue? Updating the existing pins and native lockfile is a focused solution that introduces no parallel tooling owner or application changes. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against ae8dbb2eef93. Provenance checked
TestingProof path: shipped entry point. SecurityNone. EvidenceWhat I checked:
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, 9:10 PM ET / November 21, 2026, 02:10 UTC. |
Requested by @vincentkoc.
Work sessions
Linked for team reference; these sessions aren’t public.
What Problem This Solves
The tracking worker and build pipelines use pinned dependencies, so they do not pick up compatible updates automatically. This refresh advances the pins that meet the seven-day cutoff without pulling in newer or prerelease dependency combinations.
User Impact
No CLI behavior, flags, or permissions change. The existing Pages workflow still builds and publishes the docs after a merge; this PR does not add a deployment.
Why This Change Was Made
Refresh the Node and pnpm pins used by worker CI, align the docs build with that Node version, and update the digest-pinned Dockerfile frontend. Refresh the worker’s workerd, PostCSS, Undici, and ws overrides while keeping its 24-hour repository policy, existing exclusions, and other overrides. Leave Vite on 8.3.4: resolving 8.3.8 would add two prerelease WebAssembly dependencies and one artifact newer than the fixed cutoff.
Evidence
The worker installed from the frozen lockfile on Node 26.13.1 and pnpm 11.28.12. Lint, type checking, the Wrangler dry run, all 15 tests, and a credential-free local workerd
GET /healthsmoke passed. Go’s module graph is unchanged. Independent review found no P0–P2 issues. Linuxmake ciand CLI build passed on Go 1.27.4; the full test suite and CLI build passed on the minimum supported Go series (1.26.11). Actionlint passed for both changed workflows. The hosted Docker image build and cross-platform checks are covered by PR CI; the local host has no Docker daemon.Release-age and lockfile evidence
Inclusive cutoff:
2026-11-14T01:46:00Z. Baseline:ae8dbb2eef93ef4ef123cd6cf47e3abe776bb8ce.All nine changed package identities matched the registry integrity fields; 14 changed dependency edges, with no version downgrades. The Docker frontend's OCI index hash matches the Docker Hub digest. No live Google-account tests or deployments were run.
Worked on by