chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
typescript (source)	devDependencies	major	5.9.3 → 6.0.3

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

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.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typescript@​6.0.3

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm typescript License: LicenseRef-W3C-Community-Final-Specification-Agreement - The applicable license policy does not permit this license (5) (package/ThirdPartyNoticeText.txt) From: package.json → npm/typescript@6.0.3 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@6.0.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

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 3.9s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 7 lockfile entries failed verification:
  @typescript-eslint/parser@8.59.4 was published at 2026-05-18T17:43:21.907Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/project-service@8.59.4 was published at 2026-05-18T17:42:54.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/scope-manager@8.59.4 was published at 2026-05-18T17:43:13.529Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/tsconfig-utils@8.59.4 was published at 2026-05-18T17:42:46.000Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/types@8.59.4 was published at 2026-05-18T17:42:48.708Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/typescript-estree@8.59.4 was published at 2026-05-18T17:43:04.852Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)
  @typescript-eslint/visitor-keys@8.59.4 was published at 2026-05-18T17:42:56.666Z, within the minimumReleaseAge cutoff (2026-05-18T03:11:41.240Z)

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.