chore(deps-dev): bump @types/node from 24.12.2 to 25.6.0

[dependabot]

Bumps @types/node from 24.12.2 to 25.6.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)

[greptile-apps]

Greptile Summary

This is a Dependabot-generated major version bump of @types/node from ^24 (24.12.2) to ^25 (25.6.0) across all four workspace packages, along with the transitive undici-types bump from 7.16.0 to 7.19.2. As a dev-only type definitions package, this has no runtime impact, but the jump across a major version means the type checker will now validate against Node.js v25 APIs — worth noting if the project targets Node.js v24 LTS at runtime, since v25-only APIs would pass type checks but fail at runtime.

Confidence Score: 5/5

Safe to merge — purely dev-dependency type definitions with no runtime impact.

All changes are mechanical and consistent: only @types/node specifiers and lockfile entries are updated. No runtime code is affected. The only non-trivial consideration is a Node.js version mismatch risk (v25 types vs v24 LTS runtime), but there is no pinned Node version in the repo to confirm a conflict, and this is a speculative P2 concern at most.

No files require special attention.

Important Files Changed

Filename	Overview
e2e/cli/package.json	Bumps @types/node specifier from ^24 to ^25; no other changes.
packages/arkor/package.json	Bumps @types/node specifier from ^24 to ^25; no other changes.
packages/cli-internal/package.json	Bumps @types/node specifier from ^24 to ^25; no other changes.
packages/create-arkor/package.json	Bumps @types/node specifier from ^24 to ^25; no other changes.
pnpm-lock.yaml	Lockfile updated: @types/node 24.12.2 → 25.6.0 and transitive undici-types 7.16.0 → 7.19.2 across all workspaces.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["types-node v25.6.0 (was v24.12.2)"] --> B["e2e/cli"]
    A --> C["packages/arkor"]
    A --> D["packages/cli-internal"]
    A --> E["packages/create-arkor"]
    A --> F["undici-types v7.19.2 (was v7.16.0)"]

Loading

_{Reviews (1): Last reviewed commit: "chore(deps-dev): bump @types/node from 2..." | Re-trigger Greptile}