build(deps-dev): bump @types/node from 22.19.19 to 26.2.0 - #58
build(deps-dev): bump @types/node from 22.19.19 to 26.2.0#58dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.19.19 to 26.2.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.2.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
No bugs found. Beyond the reported item, I also checked whether the @ types/node major bump could break the build directly — it's a devDependency used only for type-checking, so a mismatch with the Node 22.x runtime pinned in CI would surface as type errors during tsc/build rather than at runtime, and CI would catch it.
Extended reasoning...
The change is a mechanical dependency bump (package.json + regenerated pnpm-lock.yaml) with no source code touched. The main candidate concern already flagged is that @ types/node jumped four majors ahead of the project's Node >=22 engines requirement and the Node 22.x pinned in CI. Since @ types/node is a devDependency providing only compile-time type definitions, a version skew mainly risks type-checking errors (e.g., referencing APIs not present in the actual Node 22 runtime) rather than runtime failures, and any such issue would be caught by the existing CI type-check/build step. This keeps the risk low but not zero, so a brief informational note is appropriate rather than a full approval claim.
Bumps @types/node from 22.19.19 to 26.2.0.
Commits
Dependabot 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)