Skip to content

build(deps): refresh tracking worker and CI tooling - #1344

Open
roboclaw-bot wants to merge 2 commits into
mainfrom
openclaw/deps-seven-day-gogcli-nov21
Open

roboclaw-bot wants to merge 2 commits into
mainfrom
openclaw/deps-seven-day-gogcli-nov21

Conversation

@roboclaw-bot

Copy link
Copy Markdown
Contributor

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 /health smoke passed. Go’s module graph is unchanged. Independent review found no P0–P2 issues. Linux make ci and 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.

Candidate Verified upstream date (UTC)
actions/setup-node v7.1.0, immutable commit 2026-10-08T02:52:34Z
Node 26.13.1 (checksums) 2026-11-10 (Linux x64 artifact: 2026-11-11T00:21:15Z)
Dockerfile frontend 1.29.0 2026-11-11T21:41:20.385135Z
pnpm 11.28.12 2026-11-13T21:01:02.241Z
PostCSS 8.5.33 2026-11-13T22:46:13.565Z
Undici 8.12.4 2026-11-05T08:55:59.361Z
ws 8.23.0 2026-11-12T21:39:13.861Z
workerd 1.20261114.1 2026-11-14T01:01:46.841Z
workerd darwin x64 2026-11-14T00:55:56.561Z
workerd darwin arm64 2026-11-14T00:56:25.042Z
workerd linux x64 2026-11-14T00:55:53.821Z
workerd linux arm64 2026-11-14T00:58:39.555Z
workerd windows x64 2026-11-14T00:55:51.086Z

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

roboclaw-bot and others added 2 commits November 21, 2026 01:54
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
@roboclaw-bot
roboclaw-bot requested a review from a team as a code owner November 21, 2026 01:57
@clawsweeper

clawsweeper Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
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 clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Nov 21, 2026
@clawsweeper

clawsweeper Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge.

What this changes

This PR refreshes tracking-worker dependencies, Node and pnpm pins, setup-node, and the Dockerfile frontend.

Example: CI installs and builds the tracking worker.

  • Before: The workflow selects Node 26.12.1 and pnpm 11.28.5.
  • After: The workflow selects Node 26.13.1 and pnpm 11.28.12, matching the worker package-manager pin.

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused, useful maintenance patch supported by passing hosted checks and verified package identities, with no actionable findings.
Proof confidence 🐚 platinum hermit (4/6) This tooling-only refresh requires no user-facing behavior proof; reviewed-head hosted workflows exercise frozen worker installation, validation, and image building, while the body separately reports a local workerd health smoke.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Pinned build and worker tools require explicit maintenance to receive compatible upstream updates.
Reason: The authorized maintenance direction has a narrow diff, preserves established policies, and adds no user-facing configuration or contract.

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
Reviewed head: 9f6aa0e775ac87e2334b21a8b5c35d07c26859d8

Before merge

None.

Findings

None.

Agent review details

How this fits together

GitHub 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]
Loading

Technical review

Best 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

Testing

Proof path: shipped entry point.

Security

None.

Evidence

What I checked:

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P3: This is routine dependency maintenance with passing validation and no established urgent user-facing failure.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

  • P3: This is routine dependency maintenance with passing validation and no established urgent user-facing failure.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/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.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 20, 2026, 9:10 PM ET / November 21, 2026, 02:10 UTC.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant