chore(deps-dev): bump @types/node from 24.10.1 to 25.5.0

[dependabot]

Bumps @types/node from 24.10.1 to 25.5.0.

Commits

• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[claude]

PR Review: @types/node 24 → 25 major bump

Overview

Dependabot bumps @types/node from 24.10.1 to 25.5.0 — a major version upgrade. Only package.json and pnpm-lock.yaml are changed; undici-types also bumps from 7.16.0 → 7.18.2 as a transitive dep.

Findings

🟡 Warnings

• Major version jump (24 → 25): Node.js 25 type definitions can introduce breaking type changes (new APIs, narrowed return types, changed signatures). If the project targets a Node.js 24 LTS runtime in CI, the types may diverge from the actual runtime. Worth verifying pnpm run type-check passes cleanly with the new types.
• undici-types bump (7.16.0 → 7.18.2): Transitive but worth noting — this package powers fetch/Request/Response typings. Minor bumps here are generally safe.

👍 What's Good

• Clean, minimal diff — only lockfile and version specifier updated as expected.
• No source code changes needed, suggesting the Node 25 types are backwards compatible for this codebase.

Summary

Safe to merge if CI (Validate / type-check) passes. The major version bump is lower risk than a runtime upgrade since these are just type definitions, but I'd confirm the type-check step specifically passes before approving.