chore(deps-dev): bump @types/node from 20.19.41 to 25.9.0

[dependabot]

Bumps @types/node from 20.19.41 to 25.9.0.

Commits

• See full diff in compare view

**Disclaimer This is AxiomID Review Agent.

Greptile Summary

Automated dependabot bump of the @types/node dev dependency from ^20 (resolved 20.19.41) to ^25 (resolved 25.9.0), along with the transitive undici-types bump from 6.21.0 to 7.24.6.

• package.json specifier updated from ^20 to ^25; package-lock.json reflects the new resolved versions for both @types/node and undici-types.

Confidence Score: 5/5

Safe to merge — only dev-only type definitions are updated; no runtime code changes.

The change touches only @types/node and its transitive undici-types, both of which are dev dependencies used solely for TypeScript type checking. No runtime behaviour is altered.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Bumps @types/node devDependency specifier from ^20 to ^25
package-lock.json	Lockfile updated to reflect @types/node 25.9.0 and undici-types 7.24.6

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

[dependabot]

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the @types/node development dependency from version ^20 to ^25 in package.json. This enables Node.js type definitions compatible with version 25 and later minor releases.

Changes

Dependency Update

Layer / File(s)	Summary
Node types version bump package.json	The @types/node devDependency is updated from ^20 to ^25, allowing type definitions for Node.js version 25.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, skip, and types align,
Node's definitions, now more fine,
From twenty's nest to twenty-five,
The types stay fresh and come alive! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely a Dependabot-generated summary and lacks the required sections from the repository's description template.	Add a proper description following the template: include a 📝 Description section explaining the rationale, 🔗 Related Issue, 🧩 Type of Change selection, and ✅ Strict Checklist confirmations (Code Quality, Security & Architecture, and Testing sections).

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly and specifically describes the main change: a dependency version bump of @types/node with exact version numbers.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

---

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

[coderabbitai]

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 `@package.json`:
- Line 71: Update the devDependency for "`@types/node`" in package.json to align
with your minimum supported Node.js version by replacing the current "^25" with
a version compatible with Node.js >=22 (for example "^22" or a specific 22.x
release); after changing the version, regenerate the lockfile and install
dependencies (npm/yarn/pnpm install) so the lockfile and node_modules reflect
the new `@types/node` version and prevent using typings for newer Node.js APIs.

🪄 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bd5bb4bf-ae5b-4e9a-a0e0-d20a3ad363d1

📥 Commits

Reviewing files that changed from the base of the PR and between a241239 and 698fd85.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

What is the recommended @types/nodeversion for Node.js 22? Does@types/node version 25 exist and what Node.js version does it target?

💡 Result:

The recommended version of @types/node for Node.js 22 is the latest 22.x release [1][2][3]. The @types/node package follows a versioning convention where the major version of the package corresponds to the major version of Node.js it targets [4]. Yes, @types/node version 25 exists [1][2][3]. It targets Node.js 25 [1][2][3]. As of May 2026, the latest available version is 25.7.0 [2][3][5]. Because @types/node versions are aligned with Node.js major versions, you should install the version that matches your specific Node.js runtime major version to ensure accurate type definitions for the APIs available in your environment [4]. For example, if you are using Node.js 22, you should use @types/node@22.x [1][2][3].

Citations:

• 1: https://www.npmjs.com/package/@types/node/v/22.0.0
• 2: https://www.npmjs.com/package/@types/node
• 3: https://www.npmjs.com/package/@types/node?activeTab=versions
• 4: https://stackoverflow.com/questions/42035263/relationship-between-the-version-of-node-js-and-the-version-of-types-node
• 5: https://registry.npmjs.org/@types/node

---

🏁 Script executed:

#!/bin/bash
# Check if there are any TypeScript compilation errors with the new types
if command -v npm &> /dev/null; then
  npm list `@types/node` 2>/dev/null || echo "`@types/node` not yet installed"
  
  # Check what Node.js version is specified and compare with types version
  echo "=== Engines requirement ==="
  cat package.json | jq -r '.engines.node // "not specified"'
  
  echo "=== `@types/node` version ==="
  cat package.json | jq -r '.devDependencies["`@types/node`"] // "not found"'
fi

Repository: AIX-Format/PiWorker-OS

Length of output: 213

---

Align @types/node version with minimum Node.js requirement.

The @types/node version v25 should be v22 or higher. @types/node versions correspond to Node.js major versions—v25 provides type definitions for Node.js 25, but your project requires Node.js >=22. Using v25 allows code to compile with APIs that may not exist in Node.js 22, 23, or 24, causing runtime failures. Update to @types/node@22 (or higher within your supported range) to match your minimum Node.js version.

🤖 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 `@package.json` at line 71, Update the devDependency for "`@types/node`" in
package.json to align with your minimum supported Node.js version by replacing
the current "^25" with a version compatible with Node.js >=22 (for example "^22"
or a specific 22.x release); after changing the version, regenerate the lockfile
and install dependencies (npm/yarn/pnpm install) so the lockfile and
node_modules reflect the new `@types/node` version and prevent using typings for
newer Node.js APIs.