Update dependency upgrades - non-major

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	24.5.2 -> 24.6.2
eslint-config-upleveled	9.4.0 -> 9.4.1
pnpm (source)	10.17.1+sha512.17c560fca4867ae9473a3899ad84a88334914f379be46d455cbf92e5cf4b39d34985d452d2583baf19967fa76cb5c17bc9e245529d0b98745721aa7200ecaf7a -> 10.18.0
typescript (source)	5.9.2 -> 5.9.3

---

Release Notes

upleveled/eslint-config-upleveled (eslint-config-upleveled)

v9.4.1

Compare Source

• Switch style-prop-object to alternative, drop eslint-plugin-react (#​555) c61ef39
• Update dependency upgrades - non-major (#​553) 53e57a3
• Update dependency node to v22.20.0 (#​552) efdc1e7
• Upgrade tests 0ae1dff

---

pnpm/pnpm (pnpm)

v10.18.0

Compare Source

Minor Changes

• Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

  Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
  Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

  Related PR: #​10025.

Patch Changes

• Retry filesystem operations on EAGAIN errors #​9959.
• Outdated command respects minimumReleaseAge configuration #​10030.
• Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
• Don't fail with a meaningless error when scriptShell is set to false #​8748.
• pnpm dlx should not fail when minimumReleaseAge is set #​10037.

microsoft/TypeScript (typescript)

v5.9.3

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 4pm on thursday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.