chore(deps-dev): Bump @types/node from 22.19.19 to 26.2.0

[dependabot]

Bumps @types/node from 22.19.19 to 26.2.0.

Commits

• See full diff in compare view

[oratis]

Reviewed — not taking this one, and #281 makes that answer mechanical rather than a thing someone has to remember.

@types/node is pinned to ^22.10.0 in all seven manifests on purpose. It matches engines.node: ">=22" and the node-version: '22' that CI pins, because a types package decides which APIs the compiler accepts and therefore has to describe the oldest Node we support, not the newest released.

Moving it to ^26.2.0 while everything else still says 22 means a call added in Node 23–26 typechecks cleanly and then throws for anyone actually on 22. Tests would not catch it: CI runs 22, so only paths the tests execute would fail, and the rest ships.

This is the same defect as #262, where the typescript group swept @types/vscode to ^1.125.0 against engines.vscode: ^1.85.0. That one at least had vsce package to refuse it. Nothing refuses this one — it was on course to merge green, which is what makes it worth a guard rather than a one-off close.

Raising the floor to Node 26 may be right eventually. It drops every Node between 22 and 26 for everyone installing the CLI, so it belongs in a deliberate change that moves engines.node, the types, CI's node-version and the published engines field together — not a dependency bump.

#281 adds scripts/types-track-supported-runtime.test.ts (verified: re-applying ^26.2.0 fails all seven manifests) and tells dependabot to ignore @types/node majors only, so minor and patch inside 22.x keep flowing through the typescript group.

Closing in favour of that.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.