Skip to content

chore(deps-dev): Bump @types/node from 24.19.2 to 26.6.6 - #23

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.6.6
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-26.6.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026 •

Copy link
Copy Markdown

Bumps @types/node from 24.19.2 to 26.6.6.

Commits

@dependabot
dependabot Bot requested a review from a team as a code owner November 6, 2026 00:10
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 6, 2026
Copilot AI dynamic review requested due to automatic review settings November 6, 2026 00:10
@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Evals: passed

Suite: copilot-smoke

Lint: validated (no model execution) - Evidence

Run: passed - 1 trial - Evidence

Eval Trials Result
copilot-skill-smoke 1 passed

Quality & token summary

Eval Verdict Score Duration Tokens
copilot-skill-smoke passed 1.00 (threshold 1.00) 2418ms 33055 tokens (32982 in / 73 out)

Exact revision | Workflow run

Comment thread package.json
"devDependencies": {
"@microsoft/vally-cli": "0.19.0",
"@types/node": "24.19.0",
"@types/node": "26.6.6",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 wbreza left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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)

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 24.19.2 to 26.6.6.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.6.6
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump @types/node from 24.19.0 to 26.6.6 chore(deps-dev): Bump @types/node from 24.19.2 to 26.6.6 Nov 13, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/types/node-26.6.6 branch from 1c06e0a to c7e554a Compare November 13, 2026 14:58
@jongio

jongio commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

@dependabot ignore this major version

evals-action targets the node24 GitHub Actions runtime (engines.node: >=24 <25), so @types/node stays on the 24.x line.

@jongio jongio closed this Nov 13, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/types/node-26.6.6 branch November 13, 2026 18:19
@dependabot @github

dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you about version 26.x.x again, unless you re-open this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants