Skip to content

chore(deps-dev): bump @types/node from 24.13.2 to 26.1.1 in /docs #2345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: staging
Choose a base branch
from
Open

chore(deps-dev): bump @types/node from 24.13.2 to 26.1.1 in /docs #2345

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
"vue-json-pretty": "^2.6.0"
},
"devDependencies": {
"@types/node": "^25.9.2",
"@types/node": "^26.1.1",

@greptile-apps greptile-apps Bot Jul 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Lockfile Stays On Old Version

Changing the docs manifest to require @types/node ^26.1.1 without the matching pnpm-lock.yaml update leaves the install state inconsistent. A fresh CI run using pnpm install --frozen-lockfile can fail before the docs build runs because the lockfile still records the old 26.0.1 resolution.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: docs/package.json
Line: 22

Comment:
**Lockfile Stays On Old Version**

Changing the docs manifest to require `@types/node` `^26.1.1` without the matching `pnpm-lock.yaml` update leaves the install state inconsistent. A fresh CI run using `pnpm install --frozen-lockfile` can fail before the docs build runs because the lockfile still records the old `26.0.1` resolution.

How can I resolve this? If you propose a fix, please make it concise.

@greptile-apps greptile-apps Bot Jul 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Lockfile Still Stale This manifest now requires @types/node ^26.1.1, but the docs importer in pnpm-lock.yaml still records the old @types/node specifier and resolution. The docs Docker build runs pnpm install --frozen-lockfile, so a fresh build can stop at install time with a lockfile mismatch before the docs build starts. Please regenerate and commit the pnpm lockfile update with this dependency bump.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: docs/package.json
Line: 22

Comment:
**Lockfile Still Stale** This manifest now requires `@types/node` `^26.1.1`, but the docs importer in `pnpm-lock.yaml` still records the old `@types/node` specifier and resolution. The docs Docker build runs `pnpm install --frozen-lockfile`, so a fresh build can stop at install time with a lockfile mismatch before the docs build starts. Please regenerate and commit the pnpm lockfile update with this dependency bump.

How can I resolve this? If you propose a fix, please make it concise.

"mermaid": "^11.15.0",
"ts-morph": "^28.0.0",
"tsx": "^4.21.0",
Expand Down