chore(deps)(deps-dev): bump @types/node from 25.9.5 to 26.1.1 - #292
chore(deps)(deps-dev): bump @types/node from 25.9.5 to 26.1.1#292dependabot[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bad8cd5a24
ℹ️ 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".
| "@types/lodash": "^4.17.0", | ||
| "@types/luxon": "^3.4.0", | ||
| "@types/node": "^25.9.1", | ||
| "@types/node": "^26.0.1", |
There was a problem hiding this comment.
Update bun.lock with @types/node 26
When CI installs dependencies for the touched workspace, the checked-in lockfile still records @types/node as ^25.9.1 and resolves @types/node@25.9.4, while this manifest now requires ^26.0.1. The repo workflows I checked (lint-ts.yml, test-coverage.yml, and docs.yml) run bun install --frozen-lockfile, and bun install --help says that flag disallows lockfile changes, so this version bump will require a lockfile update during CI instead of using the committed lockfile.
Useful? React with 👍 / 👎.
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 25.9.5 to 26.1.1. - [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.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
bad8cd5 to
c5f34ff
Compare
Bumps @types/node from 25.9.5 to 26.1.1.
Commits