Repository navigation
build(deps): refresh stabilized runtime and browser tooling - #573
Conversation
Update provider, HTTP, media, Preact, Playwright and Oxc/test dependencies after the seven-day hold. Keep Node 24, pnpm, and all security overrides unchanged. Incorporates and extends #569. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
🦞👀 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. |
|
Codex review: needs changes before merge. What this changesUpdates stabilized runtime, browser, and development dependencies across the CLI, core library, and extension. Example: Install the workspace using pnpm install --frozen-lockfile.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Partial Merge readiness⛔ Needs changes before merge - 1 item remains Keep this maintainer-authored PR open: the dependency refresh is useful, but its LinkeDOM manifest update is missing from the lockfile. Priority: P3 Before merge
Findings
Agent review detailsHow this fits togetherWorkspace manifests and the lockfile select libraries used by the CLI, extraction core, daemon, and browser extension to turn content into summaries and media results. flowchart TD
A[Package manifests] --> B[Dependency lockfile]
B --> C[CLI and daemon]
B --> D[Core extraction]
B --> E[Browser extension]
C --> F[User results]
D --> F
E --> F
Technical reviewBest possible solution: Resolve the intended LinkeDOM update in the existing lockfile while preserving the stabilization hold, security overrides, and current application behavior. Do we have a high-confidence way to reproduce the issue? The manifest, workspace override, and lockfile directly establish that frozen workspace installs retain LinkeDOM 0.18.13; no target code or tests were run. Is this the best way to solve the issue? Updating the existing lockfile is the smallest complete repair and makes workspace validation exercise the dependency now required by the published core manifest. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 937657c257cf. Provenance checked
TestingProof path: in-process harness. SecurityNone. EvidenceAcceptance criteria:
What 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. Review metrics
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 14, 2026, 2:04 AM ET / 07:04 UTC. |
Refresh stabilized provider, HTTP, media, Preact, Playwright, and Oxc/test dependencies. This includes every update from #569 and newer eligible patch/minor versions selected from npm publication timestamps.
The seven-day adoption hold, Node 24 minimum, pnpm version, and security overrides remain unchanged. No project version bump or release is included.
Validation: lockfile generation and supply-chain policy checks pass; independent Codex P0–P2 autoreview is clean. Full Linux Node 24 build/check passed: 605 test files, 3,909 tests, 49 skipped, 94.52% line coverage and 85.67% branches. The rebased source tree is identical to the tested tree. Exact-head GitHub CI is required before merge.
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
CI hold (2026-11-14 07:28 UTC): all checks except
macos-release-buildpassed. The requiredxcode-27job is still queued after eight bounded status checks over 35 minutes. This PR is ready for the remaining platform proof; it has not been merged.