chore(deps-dev): bump @types/node from 25.9.5 to 26.1.1 in /packages/adapters/clawdstrike-origin-core#511
Conversation
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.1.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4ec4548ed9
ℹ️ 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".
| }, | ||
| "devDependencies": { | ||
| "@types/node": "^25.2.0", | ||
| "@types/node": "^26.1.1", |
There was a problem hiding this comment.
Keep the workspace lockfile in sync
This workspace is also recorded in the root lockfile, but package-lock.json still lists packages/adapters/clawdstrike-origin-core with @types/node as ^25.2.0 and locks 25.9.1 while this line now requires ^26.1.1. I checked the release workflow and it runs npm ci --ignore-scripts at the repo root (.github/workflows/release.yml:359-361); npm's ci docs state that when lockfile dependencies do not match package.json, it exits with an error instead of updating the lockfile. Please refresh and commit the root package-lock.json with this bump so workspace installs remain reproducible.
Useful? React with 👍 / 👎.
Bumps @types/node from 25.9.5 to 26.1.1.
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)