Bump @types/node from 20.11.17 to 25.9.1#24
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.11.17 to 25.9.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: 25.9.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughWalkthroughThe ChangesDependency Updates
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web/package.json`:
- Line 17: package.json requests `@types/node`@25.9.1 but the lockfile still pins
20.11.17 so CI/install will not pick up the bump; update the lockfile by
installing the requested dev dep and committing the updated lockfile: in the
project workspace run npm install --save-dev `@types/node`@25.9.1 (or npm ci
followed by npm install `@types/node`@25.9.1) to regenerate package-lock.json,
verify package-lock.json now references 25.9.1 instead of 20.11.17, and commit
the updated package-lock.json alongside the package.json change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: c5311424-1428-422d-b8be-fe4686cca861
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
web/package.json
| }, | ||
| "devDependencies": { | ||
| "@types/node": "20.11.17", | ||
| "@types/node": "25.9.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python - <<'PY'
import json
from pathlib import Path
pkg = json.loads(Path("web/package.json").read_text())
lock = json.loads(Path("web/package-lock.json").read_text())
pkg_ver = pkg["devDependencies"]["`@types/node`"]
lock_root_ver = lock.get("packages", {}).get("", {}).get("devDependencies", {}).get("`@types/node`")
lock_node_mod_ver = lock.get("packages", {}).get("node_modules/@types/node", {}).get("version")
print("package.json `@types/node`:", pkg_ver)
print("lockfile root devDependency `@types/node`:", lock_root_ver)
print("lockfile node_modules/@types/node version:", lock_node_mod_ver)
if pkg_ver != lock_root_ver or pkg_ver != lock_node_mod_ver:
print("MISMATCH: lockfile is not aligned with package.json")
raise SystemExit(1)
print("OK: lockfile matches package.json")
PYRepository: p-to-q/aleph
Length of output: 243
Fix lockfile/package.json mismatch for @types/node
web/package.jsonrequests@types/node@25.9.1, butweb/package-lock.jsonstill pins@types/node@20.11.17(root andnode_modules), sonpm ciwon’t apply the bump.- Regenerate and commit
web/package-lock.json(e.g., runnpm install -D@types/node@25.9.1inweb/so the lockfile updates).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@web/package.json` at line 17, package.json requests `@types/node`@25.9.1 but
the lockfile still pins 20.11.17 so CI/install will not pick up the bump; update
the lockfile by installing the requested dev dep and committing the updated
lockfile: in the project workspace run npm install --save-dev `@types/node`@25.9.1
(or npm ci followed by npm install `@types/node`@25.9.1) to regenerate
package-lock.json, verify package-lock.json now references 25.9.1 instead of
20.11.17, and commit the updated package-lock.json alongside the package.json
change.
|
Superseded by #28. |
Bumps @types/node from 20.11.17 to 25.9.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)