Repository navigation
chore: refresh SQLite runtime and build dependencies - #337
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: 608060ea-d65d-4184-a87d-7f13e371917e
|
🦞👀 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 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
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete 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 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherGo 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
Technical reviewBest 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
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:55 PM ET / November 21, 2026, 03:55 UTC. |
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.js26.13.1LTS patch, and pin the Dockerfile frontend to the immutable1.29.0image digest. Leave the overlapping dependency updates already onmainalone.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.modernc.org/libc v1.81.0modernc.org/cc/v4 v4.34.0modernc.org/ccgo/v4 v4.39.0v26.13.1e9c27761.29.0f55949dccandccgoare 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