Skip to content

chore(deps): update dependency @types/node to v26 - #163

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-26.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-26.x

Conversation

@renovate

@renovate renovate Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 25.9.9 → 26.6.5 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This PR is a routine Renovate devDependency bump of @types/node from 25.9.9 to 26.6.5, applied consistently across package.json and package-lock.json (including the matching undici-types transitive range). No inline issues were flagged — it's a dev-only, type-level change with no runtime impact, so it's good to merge.

I also left one optional follow-up note in the details below.

Optional follow-up note (1)
  • P3 package.json:75: @types/node@26 describes the Node 26 API surface, but this package's minimum supported runtime is Node 24 (.nvmrc, engines.node >=24, and the Node 24 job in test.yml). With these types, npm run type-check can pass for code that uses Node 26-only APIs, which then fails at runtime on Node 24. Pinning @types/node to the 24.x line keeps the type-check aligned with the minimum supported engine — or, if you intend to track the latest types deliberately, consider raising engines to match.

Share Feedback • Review Logs

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant