Repository navigation
build(deps): refresh development tools and FreeBSD action - #1090
Conversation
Update tar to 7.5.23, Vite to 8.3.8, and vmactions/freebsd-vm to 1.6.0 while retaining the existing runtime floors and security overrides.
|
🦞👀 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 Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Codex review: needs maintainer review before merge. What this changesThis PR updates tar, Vite, and the pinned FreeBSD VM action, and gives one lock stress test a 15-second timeout. Example: A contributor installs the pinned development dependencies.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review Keep this PR open: the tooling refresh is absent from current main, and the reviewed diff introduces no actionable defect; platform CI is still finishing. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherDevelopment dependencies support archive fixtures, package verification, and test execution, while the FreeBSD workflow builds and qualifies native packages in pinned guests. flowchart LR
A[Package manifest] --> B[pnpm dependency graph]
B --> C[Archive and package tooling]
B --> D[Vitest and coverage]
E[FreeBSD workflow] --> F[Pinned VM action]
F --> G[Native package qualification]
Technical reviewBest possible solution: Land this focused refresh once the existing final-head CI gates pass. Do we have a high-confidence way to reproduce the issue? Source confirms the 10-second lock deadline exceeds the existing default harness timeout; this review did not execute target code or independently reproduce the reported Windows failure. Is this the best way to solve the issue? Updating the existing pins and extending only the affected test deadline is a small, complete maintenance change that preserves the safety assertions. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against bcf9a4a4e2c1. 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. Root-cause clusterRelationship: Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. 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 13, 2026, 9:55 PM ET / November 14, 2026, 02:55 UTC. |
|
Landed as eac3b66. Final-head CI passed all 57 executed checks: https://github.com/openclaw/fs-safe/actions/runs/43547713484. Independent P2 review was clean. Full Linux Release verification was dispatched only with |
Refresh development tools to tar 7.5.23 and Vite 8.3.8, and the FreeBSD VM action to 1.6.0. This consolidates #1084 and #1089 on current main, retaining the Node runtime floor, two-day release cooldown, and existing security overrides. No package versions or public APIs change.
CI exposed an existing stress-test deadline mismatch on Windows: the harness aborted after 5 seconds while each lock attempt permits 10 seconds. Allow this one test 15 seconds to settle its lock attempts and verify cleanup. Production deadlines and all ownership/assertion checks remain unchanged.
Validation: independent Codex autoreview through P2 of the complete final diff is scoped-clean;
git diff --checkpasses. Before the test-only deadline fix, fullpnpm checkpassed on Linux (802 test files, 14,915 tests), including build, WASM allocator, compiled documentation, and installed-package checks. The affected stress test passes after the fix. The fresh-machine setup used the documented WASI SDK 34 and pinned .NET SDK 8.0.425. Exact final-head cross-platform CI must pass before merge.Related: #1084, #1089.