chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 6.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source

---

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

---

[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: @phenomnomnominal/tsquery@6.1.4
npm warn Found: typescript@6.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"6.0.2" from the root project
npm warn   12 more (cosmiconfig, cosmiconfig-typescript-loader, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@"^3 || ^4 || ^5" from @phenomnomnominal/tsquery@6.1.4
npm warn node_modules/@phenomnomnominal/tsquery
npm warn   @phenomnomnominal/tsquery@"~6.1.4" from @nx/eslint-plugin@22.5.4
npm warn   node_modules/@nx/eslint-plugin
npm warn   2 more (@nx/jest, @nx/webpack)
npm warn
npm warn Conflicting peer dependency: typescript@5.9.3
npm warn node_modules/typescript
npm warn   peer typescript@"^3 || ^4 || ^5" from @phenomnomnominal/tsquery@6.1.4
npm warn   node_modules/@phenomnomnominal/tsquery
npm warn     @phenomnomnominal/tsquery@"~6.1.4" from @nx/eslint-plugin@22.5.4
npm warn     node_modules/@nx/eslint-plugin
npm warn     2 more (@nx/jest, @nx/webpack)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@8.57.1
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"6.0.2" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@9.0.1
npm error   node_modules/@commitlint/load/node_modules/cosmiconfig
npm error     cosmiconfig@"^9.0.1" from @commitlint/load@20.5.0
npm error     node_modules/@commitlint/load
npm error       @commitlint/load@"^20.5.0" from @commitlint/cli@20.5.0
npm error       node_modules/@commitlint/cli
npm error         dev @commitlint/cli@"20.5.0" from the root project
npm error     peer cosmiconfig@">=9" from cosmiconfig-typescript-loader@6.2.0
npm error     node_modules/@commitlint/load/node_modules/cosmiconfig-typescript-loader
npm error       cosmiconfig-typescript-loader@"^6.1.0" from @commitlint/load@20.5.0
npm error       node_modules/@commitlint/load
npm error         @commitlint/load@"^20.5.0" from @commitlint/cli@20.5.0
npm error         node_modules/@commitlint/cli
npm error   11 more (cosmiconfig-typescript-loader, @swc-node/register, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.0.0" from @typescript-eslint/eslint-plugin@8.57.1
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   peer @typescript-eslint/eslint-plugin@">=6.0.0" from eslint-config-xo-typescript@1.0.1
npm error   node_modules/eslint-config-xo-typescript
npm error     peer eslint-config-xo-typescript@"^1" from @clipboard-health/eslint-config@7.3.23
npm error     packages/eslint-config
npm error       @clipboard-health/eslint-config@7.3.23
npm error       node_modules/@clipboard-health/eslint-config
npm error   peerOptional @typescript-eslint/eslint-plugin@"^8.0.0" from eslint-plugin-jest@29.15.0
npm error   node_modules/eslint-plugin-jest
npm error     peer eslint-plugin-jest@"^29" from @clipboard-health/eslint-config@7.3.23
npm error     packages/eslint-config
npm error       @clipboard-health/eslint-config@7.3.23
npm error       node_modules/@clipboard-health/eslint-config
npm error   1 more (@clipboard-health/eslint-config)
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.4 <6.0.0" from @typescript-eslint/eslint-plugin@8.57.1
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     peer @typescript-eslint/eslint-plugin@">=6.0.0" from eslint-config-xo-typescript@1.0.1
npm error     node_modules/eslint-config-xo-typescript
npm error       peer eslint-config-xo-typescript@"^1" from @clipboard-health/eslint-config@7.3.23
npm error       packages/eslint-config
npm error         @clipboard-health/eslint-config@7.3.23
npm error         node_modules/@clipboard-health/eslint-config
npm error     peerOptional @typescript-eslint/eslint-plugin@"^8.0.0" from eslint-plugin-jest@29.15.0
npm error     node_modules/eslint-plugin-jest
npm error       peer eslint-plugin-jest@"^29" from @clipboard-health/eslint-config@7.3.23
npm error       packages/eslint-config
npm error         @clipboard-health/eslint-config@7.3.23
npm error         node_modules/@clipboard-health/eslint-config
npm error     1 more (@clipboard-health/eslint-config)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-04-07T19_38_11_668Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-07T19_38_11_668Z-debug-0.log

[devin-ai-integration]

Devin Review found 5 new potential issues.

[devin-ai-integration]

🚩 Multiple peer dependency upper bounds exclude TypeScript 6

Beyond the lockfile being stale, even after running npm install, the following packages have peer dependency constraints that reject TypeScript 6.0.2:

• @typescript-eslint/* (7 packages): >=4.8.4 <6.0.0
• ts-jest@29.4.6: >=4.3 <6
• eslint-plugin-jest: >=4.8.4 <6.0.0
• Some nested @typescript-eslint/* in packages/eslint-plugin: >=4.8.4 <5.9.0

This means a simple lockfile regeneration won't be sufficient — these dependencies also need to be upgraded to versions that support TypeScript 6, or the install will fail with ERESOLVE errors. This is a major-version TypeScript bump that likely requires a coordinated upgrade of the tooling ecosystem.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🚩 Major version bump may require code changes across the monorepo

TypeScript 6.0 is a major version bump that likely includes breaking changes (removed deprecated APIs, stricter type checking, changed compiler behavior). While this PR only touches package.json, the monorepo contains many TypeScript packages (packages/*/src) that may need code adjustments. The typecheck script (package.json:32) runs tsgo --project tsconfig.lint.json --noEmit which would catch type errors, but there may also be runtime behavioral differences. The PR should ideally include evidence that npm run all (build, lint, test for all packages) passes after the upgrade.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 @typescript-eslint 8.57.1 peer dependency violated by TypeScript 6.0.2 (<6.0.0 required)

All @typescript-eslint/* packages at version 8.57.1 (resolved in the lockfile) declare peerDependencies.typescript: ">=4.8.4 <6.0.0". Bumping TypeScript to 6.0.2 violates this constraint. These packages are used for ESLint-based linting via @nx/eslint in per-package lint targets (run through nx run-many --targets lint), so incompatibility could cause lint failures across the monorepo.

Affected packages from package-lock.json

node_modules/@typescript-eslint/eslint-plugin: v8.57.1, ts peerDep=>=4.8.4 <6.0.0
node_modules/@typescript-eslint/parser: v8.57.1, ts peerDep=>=4.8.4 <6.0.0
node_modules/@typescript-eslint/typescript-estree: v8.57.1, ts peerDep=>=4.8.4 <6.0.0
(and other @typescript-eslint/* packages)

These are peer dependencies of packages/eslint-config/package.json which declares "@typescript-eslint/eslint-plugin": "^8.46.4" and "@typescript-eslint/parser": "^8.46.4".

Prompt for agents

The TypeScript 6.0.2 upgrade violates the @typescript-eslint/* 8.57.1 peer dependency constraint of 'typescript: >=4.8.4 <6.0.0'. These packages are used for ESLint linting across the monorepo. Either: (1) upgrade @typescript-eslint/* to a version that supports TypeScript 6 (check https://github.com/typescript-eslint/typescript-eslint/releases), or (2) hold off on the TypeScript 6 upgrade until compatible @typescript-eslint versions are available. The relevant peer dependency declarations are in packages/eslint-config/package.json.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 0 new potential issues.

View 2 additional findings in Devin Review.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🚩 Coexistence of typescript and @typescript/native-preview

The repo has both "typescript": "6.0.2" and "@typescript/native-preview": "7.0.0-dev.20260401.1" (package.json:52) in devDependencies. The typecheck script uses tsgo (from the native preview). Having both is likely intentional (standard tsc for build/jest, tsgo for type checking), but after a major version bump it's worth confirming they remain compatible and don't conflict in module resolution or type evaluation.

(Refers to lines 52-73)

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🚩 Renovate may have failed to update the lockfile

This PR was authored by renovate[bot] (git show HEAD confirms). Renovate typically updates both package.json and package-lock.json in the same commit. The fact that only package.json was changed suggests either Renovate's lockfile maintenance is misconfigured (check .github/renovate.json), or npm install failed during Renovate's PR creation — possibly because peer dependency conflicts prevented a clean install. This warrants checking the Renovate logs and configuration.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Devin Review found 0 new potential issues.

View 2 additional findings in Devin Review.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.