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

[dependabot]

Bumps @types/node from 24.13.2 to 26.1.1.

Commits

• See full diff in compare view

[greptile-apps]

Greptile Summary

This PR updates the docs workspace Node type dependency. The main change is:

• Bumps @types/node in docs/package.json to ^26.1.1.

Confidence Score: 4/5

This should be fixed before merging.

• The docs manifest and pnpm lockfile still disagree on the @types/node version.
• The docs Docker build uses a frozen pnpm install, so the install can fail before the build runs.

docs/package.json and pnpm-lock.yaml

Important Files Changed

Filename	Overview
docs/package.json	Updates the docs workspace @types/node dev dependency.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
docs/package.json:22
**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.

_{Reviews (2): Last reviewed commit: "chore(deps-dev): bump @types/node from 2..." | Re-trigger Greptile}

[greptile-apps]

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]

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.