Skip to content

chore: refresh SQLite runtime and build dependencies - #337

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

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

Conversation

@roboclaw-bot

Copy link
Copy Markdown
Contributor

What Problem This Solves

Slacrawl maintainers need to keep the SQLite runtime, the Node.js runtime for Desktop decoder tests, and the Dockerfile frontend current without bringing in releases newer than the seven-day cutoff for this sweep.

User Impact

No intended user-visible change. SQLite, the Go minimum, the preferred Go toolchain, and the container base images stay at their current versions. No migration or operator action is needed.

Why This Change Was Made

Update the libc runtime that backs SQLite to v1.81.0, move the Desktop test and Crabbox hydration jobs to the Node.js 26.13.1 LTS patch, and pin the Dockerfile frontend to the immutable 1.29.0 image digest. Leave the overlapping dependency updates already on main alone.

Evidence

The synthetic Slack export smoke test imported a fixture, built a projection, checked its expected message, and verified the output. Module checks, formatting, vet, dead-code and workflow lint checks, the vulnerability scan against an offline copy of the Go advisory database, and all four unsigned platform snapshot builds passed in credential-free Linux isolation. The local full race suite hit the time limit before completion; hosted Linux race, macOS, and Docker build/smoke checks are required before merge. No live Slack data, credentials, release, or deployment were used.

Version and artifact provenance (UTC)

Fixed inclusive cutoff: 2026-11-14T01:46:00Z; base: e6f61277c4ad8df6c0128a613f0b9895d7e729da.

Version Registry or tag provenance Artifact provenance
modernc.org/libc v1.81.0 Nov 10 12:18:53 Module ZIP Nov 10 18:28:06
modernc.org/cc/v4 v4.34.0 Nov 9 12:34:36 Module ZIP Nov 9 12:39:34
modernc.org/ccgo/v4 v4.39.0 Nov 9 14:42:34 Module ZIP Nov 9 14:56:45
Node.js v26.13.1 Tag resolves to e9c2776 Linux x64 Nov 11 00:21:15; macOS arm64 Nov 11 00:18:01; Linux SHA-256 verified
Dockerfile frontend 1.29.0 Tag and OCI source revision both resolve to f55949d Registry push Nov 11 21:41:20.385135; verified the pinned OCI index digest

cc and ccgo are the only other version changes in Slacrawl’s selected Go graph. The 33 added or changed module versions embedded in the Linux x64 Dockerfile frontend were also checked: their latest registry timestamp was Nov 6 19:57:40 and latest module ZIP timestamp was Nov 9 12:01:20.

Please keep Allow edits from maintainers enabled.

Contributed with @vincentkoc.

Work sessions

Linked for team reference; these sessions aren’t public.

Worked on by

roboclaw-bot and others added 2 commits November 21, 2026 03:37
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: 608060ea-d65d-4184-a87d-7f13e371917e
@roboclaw-bot
roboclaw-bot requested a review from a team as a code owner November 21, 2026 03:42
@clawsweeper

clawsweeper Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

🦞👀
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

Codex review: needs maintainer review before merge.

What this changes

This PR updates SQLite’s libc dependency, aligns test environments on Node.js 26.13.1, and pins Dockerfile frontend 1.29.0 by digest.

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A focused maintenance patch with successful hosted validation and no actionable findings.
Proof confidence 🌊 off-meta tidepool Not applicable: This maintenance-only change adds no intended user-visible behavior; hosted validation supports the dependency refresh without requiring new contributor media.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Maintainers need supported runtime and build dependencies without changing the archive product contract.
Reason: The authorized maintenance direction is implemented through narrow updates consistent with prior merged refreshes.

Merge readiness

✅ Ready for maintainer review

Keep this PR open: it provides a focused dependency refresh absent from main, its hosted checks pass, and no actionable correctness or security defect was found.

Priority: P3
Reviewed head: 4b9f9fbb6606524c9c35df8e5587718597cdbb77

Before merge

None.

Findings

None.

Agent review details

How this fits together

Go dependency pins supply the archive CLI’s SQLite runtime, while Node.js supports Desktop decoder tests and the Dockerfile frontend builds the container image.

flowchart TD
  A[Dependency pins] --> B[SQLite libc runtime]
  B --> C[Archive CLI]
  C --> D[SQLite archive]
  A --> E[Node decoder tests]
  A --> F[Dockerfile frontend]
  F --> G[Container build]
  G --> C
Loading

Technical review

Best possible solution:

Land the focused version refresh through the repository’s normal approval process.

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

This PR is maintenance rather than a bug report, so there is no failing user scenario to reproduce.

Is this the best way to solve the issue?

Direct version and checksum updates are appropriately scoped, keep the existing dependency owners, and avoid additional machinery.

AGENTS.md: not found in the target repository.

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

Provenance checked

  • Go runtime dependencies and checksums keeps the original intent (e6f6127: The preceding refresh selected SQLite 1.62.0 and libc 1.80.1 while preserving the Go minimum and preferred toolchain.)
  • Node versions and contributor documentation keeps the original intent (062af78: CI and hydration deliberately use matching Node versions for Desktop decoder tests; the documentation describes that environment.)
  • Dockerfile frontend keeps the original intent (06db31f: The earlier dependency refresh selected Dockerfile frontend 1.27 as build tooling.)

Security

None.

Evidence

What I checked:

  • Verified introduced changes: The pinned base-to-head diff contains only dependency versions, corresponding checksums, and the matching contributor documentation update; main still selects libc 1.80.1 and Node.js 26.13.0. (go.mod:50, 4b9f9fbb6606)
  • Hosted validation: Checks on the reviewed head report successful Linux race tests, macOS tests, dependency verification and vulnerability checks, lint, snapshot packaging, and Docker build/smoke. Downloading job logs encountered a network allowlist restriction; these are verified check conclusions, not independently inspected runtime traces. (.github/workflows/ci.yml:77, 4b9f9fbb6606)
  • Existing maintenance direction: The merged refresh at build(deps): refresh runtime libraries and secret scanner #336 supplies the current dependency baseline; this PR retains its SQLite version and Go requirements while advancing libc. Earlier Node alignment at build(deps): refresh archive dependencies and Node tooling #310 and Docker frontend maintenance at chore(deps): refresh Go toolchain and archive dependencies #168 establish the same maintenance pattern. (go.mod:53, e6f61277c4ad)
  • Policy and ownership inspection: No AGENTS.md, maintainer-notes directory, or pr-simplify skill was present. Feature history identifies Peter Steinberger’s repeated runtime refreshes and Vincent Koc’s Node provisioning and CI work; CODEOWNERS routes workflows and Go manifests to openclaw-secops. Some older history inspection encountered unavailable promisor objects, without affecting the reviewed diff or current-main evidence. (.github/CODEOWNERS:5, e6f61277c4ad)

Likely related people:

  • Peter Steinberger: Raw commit e6f6127 adds go.mod:53 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: e6f61277c4ad; files: go.mod)
  • Vincent Koc: Raw commit 04a30a6 adds .github/workflows/ci.yml:67 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 04a30a63530d; files: .github/workflows/ci.yml)

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: Routine dependency maintenance with no reported user-facing regression or urgent vulnerability.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool 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: Routine dependency maintenance with no reported user-facing regression or urgent vulnerability.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool 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, 10:55 PM ET / November 21, 2026, 03:55 UTC.

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

Labels

chore other 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.

2 participants