[dependabot]

Bumps @types/node from 24.19.0 to 26.6.6.

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)

[github-actions]

Evals: passed

Suite: copilot-smoke

Lint: validated (no model execution) - Evidence

Run: passed - 1 trial - Evidence

Eval	Trials	Result
copilot-skill-smoke	1	passed

Exact revision | Workflow run

[wbreza]

Low: Keep the Node declarations aligned with Node 24

This changes the API definitions used by TypeScript to Node 26, but package.json still requires Node 24, .node-version selects 24.21.0, and action.yml runs the Action on node24. TypeScript can now accept Node 26 APIs that the supported runtime does not provide, so the type check no longer guards against those unsupported calls. The passing checks do not show a current runtime failure; this is a gap in compile-time compatibility checking. Keep @types/node on the 24.x line and regenerate the lockfile while Node 24 remains the supported runtime.

Generated by 🌳Breza Bot

[wbreza]

Reviewed #23 at 1c06e0a. Comment — one low-severity issue remains before approval.

Keep the Node type declarations on the supported Node 24 line so type checking continues to match the Action's runtime. See the inline finding.

The manifest and lockfile changes are consistent, and the existing model-free CI checks passed for this head. No current runtime failure was found. I did not run PR scripts or install dependencies locally. The review reaction created by this run was removed.

Generated by 🌳Breza Bot

[Copilot]

🟢 Approval recommended

No active review issues remain for the dependency and lockfile update.

No open issues 🎉

1 file not reviewed

• pnpm-lock.yaml: Generated file

What changed in this PR

Updates the development-time @types/node package from 24.19.0 to 26.6.6, along with the corresponding pnpm lockfile resolutions.

Changes:

• Bumps @types/node in package.json.
• Refreshes lockfile entries, including undici-types and Vitest/Vite peer resolutions.
• Runtime configuration remains on Node 24; the Node 26 type declarations should be aligned with the supported runtime before approval.

This pull request requires changes.

File	Summary
package.json	Updates the @types/node development dependency. Moderate: Node 26 declarations may expose APIs unavailable in the project’s Node 24 runtime; keep the dependency on the Node 24 line or update the runtime configuration together.
pnpm-lock.yaml	Records the updated Node.js type package, transitive dependency, and peer-resolution entries.

_{Review effort: Lite (auto)}