chore(deps-dev): bump @types/node from 25.0.9 to 25.1.0 in /apps/admin

[dependabot]

Bumps @types/node from 25.0.9 to 25.1.0.

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[fingertips18]

@coderabbitai Are there any breaking changes in this dependency update? Is it safe to merge?

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

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

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🌐 Web query:

`@types/node` 25.1.0 changelog breaking changes

💡 Result:

• There is no published @types/node@25.1.0 (the @types/node 25 line is currently 25.0.x, e.g. 25.0.10 as of Jan 21, 2026). So there isn’t a 25.1.0-specific @types/node changelog to reference. [1]
• @types/node also doesn’t provide an official per-version “breaking changes” changelog; the usual approach is to inspect the git/npm diffs between the specific versions you’re upgrading. [2]

If you actually meant Node.js v25.1.0 (runtime): it’s a semver-minor release with “Notable Changes” listed, and it does not list any semver-major/breaking items in its release notes. [3]

Sources:
[1] Release list showing @types/node 25.x versions (25.0.x, not 25.1.0): https://releasealert.dev/npmjs/%40types/node
[2] DefinitelyTyped discussion/issue about lack of @types/node changelog: DefinitelyTyped/DefinitelyTyped#52998
[3] Node.js v25.1.0 release notes (semver-minor items): https://nodejs.org/id/blog/release/v25.1.0

---

🏁 Script executed:

#!/bin/bash
# Check if `@types/node`@25.1.0 exists in npm registry
npm view `@types/node`@25.1.0 version 2>&1 || echo "Version check failed"

# Also check what versions are available in the 25.x range
npm view `@types/node` versions --json | jq '.[] | select(startswith("25."))' | tail -20

Length of output: 115

---

🏁 Script executed:

#!/bin/bash
# Check the package.json file to see the actual version being updated to
cat apps/admin/package.json | jq '.devDependencies["@types/node"]'

Length of output: 9

---

🏁 Script executed:

#!/bin/bash
# Get more details about the version and when it was published
npm view `@types/node`@25.1.0 time
npm view `@types/node`@25.0.9 time

# Check for any deprecation warnings
npm view `@types/node`@25.1.0 deprecated 2>&1 || echo "Not deprecated"

Length of output: 187349

---

🌐 Web query:

`@types/node` 25.0.9 to 25.1.0 diff changes DefinitelyTyped

💡 Result:

As of Jan 29, 2026, there is no @types/node@25.1.0 published on npm/DefinitelyTyped—the latest 25.x is 25.0.10. [1][2]

What changed from @types/node@25.0.9 → 25.0.10

From the published package metadata on UNPKG:

• version: 25.0.9 → 25.0.10 [3][4]
• typesPublisherContentHash changed (meaning the published .d.ts content changed), but:
• typesVersions mapping stayed the same (ts5.6/*, ts5.7/*) and
• dependency undici-types stayed ~7.16.0. [3][4]

How to get the exact file-level diff (recommended)

Because DefinitelyTyped doesn’t publish a human-readable changelog per patch, do a tarball diff locally:

npm pack `@types/node`@25.0.9
npm pack `@types/node`@25.0.10
tar -xzf types-node-25.0.9.tgz  -C /tmp/node-25.0.9
tar -xzf types-node-25.0.10.tgz -C /tmp/node-25.0.10
diff -ru /tmp/node-25.0.9/package /tmp/node-25.0.10/package

If you actually meant Node.js runtime v25.1.0 (not @types/node@25.1.0), that’s a separate thing; Node v25.1.0 was released Oct 28, 2025. [5]

Sources: [1] [2] [3] [4] [5]

---

🏁 Script executed:

#!/bin/bash
# Download both package.json files to compare metadata and see what changed
npm view `@types/node`@25.0.9 --json | jq '{version, types, dependencies, peerDependencies, deprecated}' > /tmp/25.0.9.json
npm view `@types/node`@25.1.0 --json | jq '{version, types, dependencies, peerDependencies, deprecated}' > /tmp/25.1.0.json

# Show the differences
echo "=== Metadata comparison ==="
diff /tmp/25.0.9.json /tmp/25.1.0.json || true

# Check package sizes
echo -e "\n=== Package size comparison ==="
echo "25.0.9 unpacked size: $(npm view `@types/node`@25.0.9 dist.unpackedSize)"
echo "25.1.0 unpacked size: $(npm view `@types/node`@25.1.0 dist.unpackedSize)"

# Get the tarball and check file count
echo -e "\n=== Quick tarball inspection ==="
npm pack `@types/node`@25.1.0 --quiet
tar -tzf types-node-25.1.0.tgz | wc -l
echo "files in 25.1.0 tarball"

Length of output: 262

---

@fingertips18, based on my analysis, this update appears safe to merge:

Summary

@types/node@25.1.0 was published on 2026-01-28 (yesterday). This is a minor version bump (25.0.9 → 25.1.0) for TypeScript type definitions.

Key Findings

✅ No breaking changes detected:

• No dependency changes (still uses undici-types@~7.16.0)
• No deprecation warnings
• Package size increased by ~7KB (new types added, likely)
• Same TypeScript version support (ts5.6, ts5.7)

✅ Low risk:

• This is a devDependency - only affects build time, not runtime
• Minor version bumps in @types packages typically add new types or update existing definitions to match newer Node.js APIs
• Won't affect your application's runtime behavior

Recommendation

Safe to merge. Since this is a type-only package for development, the worst case is potential TypeScript compilation warnings if you're using types that changed. Given it's a minor version bump following semantic versioning conventions, breaking changes are unlikely.

You might want to:

1. Run npm run build (or your TypeScript compilation command) locally after updating to verify no type errors
2. Run your test suite to ensure everything passes

The update is primarily to keep your types aligned with the latest Node.js API definitions.

[dependabot]

Superseded by #864.