chore(deps)(deps-dev): bump @types/node from 24.13.3 to 26.1.2

[dependabot]

Bumps @types/node from 24.13.3 to 26.1.2.

Commits

• See full diff in compare view

[pathosDev]

Declining this one — @types/node tracks the engines support floor on purpose, not latest.

ac552d5b chore(deps)!: raise runtime floors states it outright:

@types/node is pinned to the support floor (24) instead of latest so we cannot accidentally use newer-Node APIs.

Reinforced by package.json (engines.node: ">=24.0.0") and by .github/workflows/multi-runtime.yml, which pins its Node leg to '24' with the comment "24 deliberately — it is the engines floor we claim to support."

The red checks are not the reason

They are the usual missing bun.lock sync (error: lockfile had changes, but lockfile is frozen) — tracked separately in #817. I synced the lockfile locally so the bump could actually be evaluated on its merits.

Why the pin is load-bearing

With the bump applied and the lockfile synced, every gate passes:

• bun run typecheck — green
• bun test — green, 3544 pass / 0 fail across 296 files

That is not evidence the bump is safe; it is the reason the pin exists. Its job is to make newer-Node APIs unrepresentable at compile time, not to fail a test. Installing both type majors side by side and compiling the same file against each shows the difference:

import { connect } from 'node:quic';
import { convertProcessSignalToExitCode } from 'node:util';

=== @types/node 24.13.3 ===
error TS2307: Cannot find module 'node:quic' or its corresponding type declarations.
error TS2305: Module '"node:util"' has no exported member 'convertProcessSignalToExitCode'.

=== @types/node 26.1.2 ===
(clean)

@types/node 26 declares whole modules Node 24 does not have (ffi.d.ts, quic.d.ts). Under this bump such code compiles and ships, then crashes on the runtime floor we advertise.

So it stops coming back

This is the fourth reopening of a settled decision — #334, #336 and #374 were closed, #340 briefly landed on 26.1.0 before ac552d5b rolled it back. develop now carries an ignore condition for @types/node majors (#906), so minor and patch updates inside the pinned major keep flowing while the major stops being re-proposed. When the floor is raised deliberately, the pin and the rule move together.

[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.