chore(deps-dev): bump the development group across 1 directory with 4 updates - #29
dependabot[bot] wants to merge 1 commit into
Conversation
… updates Bumps the development group with 4 updates in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt), [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint) and [tsdown](https://github.com/rolldown/tsdown). Updates `@types/node` from 26.4.0 to 26.4.1 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `oxfmt` from 0.65.0 to 0.66.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.66.0/npm/oxfmt) Updates `oxlint` from 1.80.0 to 1.81.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.81.0/npm/oxlint) Updates `tsdown` from 0.22.14 to 0.23.0 - [Release notes](https://github.com/rolldown/tsdown/releases) - [Commits](rolldown/tsdown@v0.22.14...v0.23.0) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.4.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development - dependency-name: oxfmt dependency-version: 0.66.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: oxlint dependency-version: 1.81.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development - dependency-name: tsdown dependency-version: 0.23.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development ... Signed-off-by: dependabot[bot] <[email protected]>
|
🦞👀 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. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Codex review: blocked before merge. Reviewed September 14, 2026, 3:01 PM ET / 19:01 UTC (Revision 7). ClawSweeper reviewWhat this changesUpdates Node.js types, formatting, linting, and package-building development dependencies and their lockfile resolutions. Regression provenancePossible regression — suspected (reviewed change). No predecessor PR is attributed. Merge readiness⛔ Blocked before merge - 3 items remain The update remains distinct from main and useful, but the previously reported Node 25 development-install compatibility gap remains unresolved. Priority: P2 Review scores
Verification
How this fits togetherThe development toolchain checks the router’s TypeScript source and produces its published JavaScript and type declarations. Contributors and CI install these tools through pnpm before building and validating the package. flowchart LR
A[Contributor Node version] --> B[pnpm engine checks]
C[Locked development tools] --> B
B --> D[Build and quality checks]
E[Router source] --> D
D --> F[JavaScript and declarations]
F --> G[Package import validation]
Before merge
Findings
Agent review detailsSecurityNone. Review metrics
Merge-risk optionsMaintainer options:
Copy recommended automerge instructionTechnical reviewBest possible solution: Keep the tooling update with explicit development Node requirements and a Node 25 migration note, preserving the published router’s runtime engine range. Do we have a high-confidence way to reproduce the issue? Yes, from source: installing this head’s development dependencies on Node 25 conflicts with two newly narrowed engine ranges under engine-strict. Installation was not executed in this read-only review. Is this the best way to solve the issue? The dependency update is reasonable, but incomplete as submitted: separate development requirements from runtime support and document the migration instead of narrowing consumer runtime engines. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against ea06377b0e80. LabelsLabel justifications:
EvidenceAcceptance criteria:
What I checked:
Likely related people:
Rank-up movesOptional improvements that raise the rating; they are not merge blockers.
Rating scale
Overall follows the weaker of proof and patch quality. Workflow
HistoryReview history (6 earlier review cycles)
|
Bumps the development group with 4 updates in the / directory: @types/node, oxfmt, oxlint and tsdown.
Updates
@types/nodefrom 26.4.0 to 26.4.1Commits
Updates
oxfmtfrom 0.65.0 to 0.66.0Commits
0b4e2e6release(apps): oxlint v1.81.0 && oxfmt v0.66.0 (#26199)5ff57f8fix(formatter/sort-imports): handle custom side effect groups (#26217)63bc313chore(npm): update funding URL (#26066)Updates
oxlintfrom 1.80.0 to 1.81.0Release notes
Sourced from oxlint's releases.
... (truncated)
Changelog
Sourced from oxlint's changelog.
... (truncated)
Commits
0b4e2e6release(apps): oxlint v1.81.0 && oxfmt v0.66.0 (#26199)d5be037docs(linter/typescript/switch-exhaustiveness-check): clarify default case com...63bc313chore(npm): update funding URL (#26066)Updates
tsdownfrom 0.22.14 to 0.23.0Release notes
Sourced from tsdown's releases.
... (truncated)
Commits
ced9a2cchore: release v0.23.0f5f9ea9docs: add Ember support guide (#1043)8ac89dcchore: upgrade Vitest to v596a4098feat: expose programmatic watch controls (#1062)61718d7chore: upgrade depsd04119cchore: upgrade deps55f89c5chore(deps): update pnpm to v12.1.0 (#1060)946224dfix: ignore optional dependencies in type definitions62f01cdchore: release v0.23.0-rc.1bf53f43fix(cli): camel-case nested flag keysDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions