chore(renovate): Update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.8.3 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: tsconfck@3.1.6
npm warn Found: typescript@6.0.3
npm warn node_modules/typescript
npm warn   dev typescript@"^6.0.0" from the root project
npm warn   1 more (@trpc/server)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional typescript@"^5.0.0" from tsconfck@3.1.6
npm warn node_modules/tsconfck
npm warn   tsconfck@"^3.0.3" from vite-tsconfig-paths@6.0.4
npm warn   node_modules/vite-tsconfig-paths
npm warn
npm warn Conflicting peer dependency: typescript@5.9.3
npm warn node_modules/typescript
npm warn   peerOptional typescript@"^5.0.0" from tsconfck@3.1.6
npm warn   node_modules/tsconfck
npm warn     tsconfck@"^3.0.3" from vite-tsconfig-paths@6.0.4
npm warn     node_modules/vite-tsconfig-paths
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: tsdown@0.19.0
npm error Found: typescript@6.0.3
npm error node_modules/typescript
npm error   dev typescript@"^6.0.0" from the root project
npm error   peer typescript@">=5.7.2" from @trpc/server@11.8.1
npm error   node_modules/@trpc/server
npm error     peerOptional @trpc/server@"^10.45.2 || ^11.0.1" from trpc-cli@0.12.2
npm error     node_modules/trpc-cli
npm error       trpc-cli@"^0.12.2" from ultracite@7.0.11
npm error       node_modules/ultracite
npm error         dev ultracite@"^7.0.0" from the root project
npm error     @trpc/server@"^11.8.1" from ultracite@7.0.11
npm error     node_modules/ultracite
npm error       dev ultracite@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.0.0" from tsdown@0.19.0
npm error node_modules/tsdown
npm error   dev tsdown@"^0.19.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.0.0" from tsdown@0.19.0
npm error   node_modules/tsdown
npm error     dev tsdown@"^0.19.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-04T14_17_00_743Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-04T14_17_00_743Z-debug-0.log

[changeset-bot]

⚠️ No Changeset found

Latest commit: cfadc0e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.