Repository navigation
chore(deps): refresh compatible packages and patch advisories - #3953
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🦞👀 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 direct Zod to 4.6.6 and resolves three TanStack dependencies to Zod 4.6.7. Review scores
ProductKind: Maintenance · Worth it: Yes Merge readiness✅ Ready for maintainer review Keep this PR open: current main still uses Zod 4.6.5, and the dependency update has no identified blocking findings. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherZod validates scanner reports and search-classification output, while TanStack uses it for tooling configuration; validated values feed existing backend and build paths. flowchart TD
A[Dependency manifest and lockfile] --> B[Zod]
B --> C[Scanner report validation]
B --> D[Search output validation]
B --> E[TanStack tooling]
C --> F[Existing backend records]
D --> F
Technical reviewBest possible solution: Land the scoped dependency update through the existing dependency maintenance path. Do we have a high-confidence way to reproduce the issue? This PR reports no ClawHub defect requiring reproduction; inspection verifies the dependency versions and upstream changes without executing target code. Is this the best way to solve the issue? Updating the manifest and lockfile is the appropriate maintenance approach; vendoring the upstream fix or adding application workarounds would introduce unnecessary parallel ownership. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against 6a58bbfafae4. Provenance checked
TestingProof path: shipped entry point. SecurityNone. EvidenceWhat I checked:
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 October 14, 2026, 5:08 PM ET / 21:08 UTC. |
Update maintained dependency lines and security overrides while retaining the CLI Node support floor and current framework major versions. Preserve the generic component registration return type introduced by convex-test.
eae9781 to
409128a
Compare
Refresh ClawHub's supported dependency lines and remove 11 of the 12 advisory records reported by the baseline audit. This updates React/TanStack/Radix, email tooling, CLI MIME handling, Oxc and test tooling, and patches the existing DOMPurify, Next.js preview, and shell-quote overrides plus source-map-js. The convex-test update also needs its component-upgrade test wrapper to preserve the new generic registration return type.
The CLI retains Node >=22 and Undici 7, and the existing compiler arrangement is unchanged. Mermaid 12 (#3954), OIDC 4 (#3955), and the newer Nitro beta remain separate work. The remaining low KaTeX advisory comes through Mermaid 11; no audit ignore was added and no incompatible KaTeX override was forced.
Validation:
bun run ci:staticpassed, including formatting, type-aware lint and all configured Knip passes.bun run ci:types-buildandbunx tsc -p convex/tsconfig.json --noEmitpassed, including schema/CLI TypeScript checks and the production build.bun run ci:unitpassed 7,755 tests with 11 failures in six files. All 131 tests in those six files passed when rerun with two workers and temporary folders outside the checkout; the failures were timeouts/cascades and fixture environment effects. The component-upgrade test also passed independently.No production deployment or package publication is part of this PR.