chore(deps-dev): bump @types/node from 24.13.2 to 26.0.1

[dependabot]

Bumps @types/node from 24.13.2 to 26.0.1.

Commits

• See full diff in compare view

[kalwalt]

Deliberately left out of #621, which resolved the rest of the dependency backlog.

This bump is 24.x → 26.x, a major. @types/node majors describe a specific Node major's
API surface, and this project currently targets Node 22–24:

• .nvmrc → 24.15.0
• .github/workflows/publish.yml → 22.15.1

Types running ahead of the runtime let code typecheck cleanly against APIs that do not exist
when it executes. That failure is silent at build time and only appears at runtime, which
makes it a poor trade for a bump carrying no security advisory — unlike everything else
in #621, which closed real ones.

Keeping @types/node on 24.x to match .nvmrc.

Worth revisiting once #624 settles which Node versions this project actually supports — that
decision determines the right @types/node major. If the floor moves to 26, this should be
merged at the same time.

Leaving the PR open rather than closing it, so dependabot does not simply reopen it.

[kalwalt]

Closing in favour of #638, which bumps @types/node to 24.13.6 instead.

The 26.0.1 bump proposed here would put the type definitions two majors ahead of the runtime:

• .nvmrc pins Node 24 (fix: align Node version across workflows and loosen the .nvmrc pin #636), and all three workflows now resolve Node from it
• package.json declares "@types/node": "^24.13.2", so 26 breaks out of the declared range

Types for Node 26 on a Node 24 runtime means TypeScript accepts APIs that do not exist when the code runs, which quietly costs us the compiler's ability to catch a real mistake. 24.13.6 is the newest 24.x and sits inside the existing caret, so it is a lockfile-only change.

When the project moves to Node 26, .nvmrc and @types/node should 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.