chore(deps): update dependency @types/node to v24

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
@types/node (source)	devDependencies	major	22.19.19 → 24.12.4

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[cubic-dev-ai]

No issues found across 2 files

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​node@​22.19.17 ⏵ 24.12.2	+1		+1

View full report

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (557 entries)...
✗ Lockfile failed supply-chain policy check (557 entries in 10.6s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 7 lockfile entries failed verification:
  @typescript-eslint/parser@8.59.4 was published at 2026-05-18T17:43:20.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/project-service@8.59.4 was published at 2026-05-18T17:42:54.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/scope-manager@8.59.4 was published at 2026-05-18T17:43:11.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/tsconfig-utils@8.59.4 was published at 2026-05-18T17:42:46.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/types@8.59.4 was published at 2026-05-18T17:42:47.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/typescript-estree@8.59.4 was published at 2026-05-18T17:43:02.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)
  @typescript-eslint/visitor-keys@8.59.4 was published at 2026-05-18T17:42:54.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:10:34.249Z)

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.