chore(deps-dev): bump @types/node from 22.20.0 to 26.1.0#70
chore(deps-dev): bump @types/node from 22.20.0 to 26.1.0#70dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.20.0 to 26.1.0. - [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.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 719b03da8f
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@playwright/test": "1.55.1", | ||
| "@types/chrome": "^0.0.320", | ||
| "@types/node": "^22.13.0", | ||
| "@types/node": "^26.1.0", |
There was a problem hiding this comment.
This repo still targets and tests Node 22 (package.json engines, .nvmrc, and the CI setup all pin/minimum 22.13.0), but this bump makes TypeScript validate scripts and config against the Node 26 API surface. In that supported Node 22 environment, future changes can now type-check while calling Node 26-only globals/modules/options and then fail at runtime in CI or for contributors using the documented runtime; keep @types/node on the Node 22 major unless the runtime target is upgraded at the same time.
Useful? React with 👍 / 👎.
|
Closed intentionally rather than merged. Pack's runtime and CI baseline remain Node 22 (, package engines, and workflow setup), so adopting @types/node@26 would make local types drift from the supported runtime. Revisit this when Pack deliberately moves its Node baseline. |
|
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 If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
Correction to the close rationale: Pack runtime and CI baseline remain Node 22, as shown by |
1 participant
Bumps @types/node from 22.20.0 to 26.1.0.
Commits
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)