chore(deps-dev): Bump @types/node from 25.9.3 to 26.1.1

[dependabot]

Bumps @types/node from 25.9.3 to 26.1.1.

Commits

• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e6af7af2-eaf0-4700-beb3-3c47fd3f02bc

📥 Commits

Reviewing files that changed from the base of the PR and between 9811798 and 87650a8.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

📜 Recent review details

⚠️ CI failures not shown inline (2)

GitHub Actions: CI / quality: chore(deps-dev): Bump @types/node from 25.9.3 to 26.1.1

Conclusion: failure

View job details

##[group]Run pnpm install --frozen-lockfile
 �[36;1mpnpm install --frozen-lockfile�[0m
 shell: /usr/bin/bash -e {0}
 env:
   PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
 ##[endgroup]
 ? Verifying lockfile against supply-chain policies (433 entries)...
 Lockfile is up to date, resolution step is skipped
 Progress: resolved 1, reused 0, downloaded 0, added 0
 Packages: +326
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 Progress: resolved 326, reused 0, downloaded 38, added 0
 Progress: resolved 326, reused 0, downloaded 131, added 8
 Progress: resolved 326, reused 0, downloaded 269, added 20
 Progress: resolved 326, reused 0, downloaded 324, added 73
 ✗ Lockfile failed supply-chain policy check (433 entries in 5s)
 Progress: resolved 326, reused 0, downloaded 326, added 325
 Progress: resolved 326, reused 0, downloaded 326, added 326, done
 [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
   `@types/node`@26.1.1 was published at , within the minimumReleaseAge cutoff ()
 The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
 ##[error]Process completed with exit code 1.

---

GitHub Actions: CI / 0_quality.txt: chore(deps-dev): Bump @types/node from 25.9.3 to 26.1.1

Conclusion: failure

View job details

##[group]Run pnpm install --frozen-lockfile
 �[36;1mpnpm install --frozen-lockfile�[0m
 shell: /usr/bin/bash -e {0}
 env:
   PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
 ##[endgroup]
 ? Verifying lockfile against supply-chain policies (433 entries)...
 Lockfile is up to date, resolution step is skipped
 Progress: resolved 1, reused 0, downloaded 0, added 0
 Packages: +326
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 Progress: resolved 326, reused 0, downloaded 38, added 0
 Progress: resolved 326, reused 0, downloaded 131, added 8
 Progress: resolved 326, reused 0, downloaded 269, added 20
 Progress: resolved 326, reused 0, downloaded 324, added 73
 ✗ Lockfile failed supply-chain policy check (433 entries in 5s)
 Progress: resolved 326, reused 0, downloaded 326, added 325
 Progress: resolved 326, reused 0, downloaded 326, added 326, done
 [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
   `@types/node`@26.1.1 was published at , within the minimumReleaseAge cutoff ()
 The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
 ##[error]Process completed with exit code 1.

🧰 Additional context used

📓 Path-based instructions (1)

{package.json,pnpm-lock.yaml,.npmrc}

📄 CodeRabbit inference engine (CLAUDE.md)

Use pnpm as the package manager (pnpm 10.25)

Files:

• package.json

🔇 Additional comments (1)

package.json (1)

64-64: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated a development dependency to a newer version.

Walkthrough

The @types/node devDependency version constraint in package.json was updated from ^25.9.3 to ^26.1.1.

Changes

Dependency Update

Layer / File(s)	Summary
Bump @types/node version package.json	The @types/node devDependency constraint is updated from ^25.9.3 to ^26.1.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A hop, a skip, a version bump,
^26.1.1 in one small lump,
No code to chase, no bugs to find,
Just types refreshed and peace of mind. 🐇

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description lacks the required template sections for Summary, Test plan, Breaking changes, and Related.	Add the template sections with 1-3 summary bullets, a test plan checklist, breaking-change notes if any, and related issue links.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the dependency bump and version change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/npm_and_yarn/types/node-26.1.1

---

_{Comment @coderabbitai help to get the list of available commands.}