chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.0.0 → ^6.0.0
typescript (source)	^5.4.0 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • "after 9am and before 5pm Monday"

🚦 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 these updates 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 artifacts 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: prisma/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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.4.6
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   peerOptional typescript@">=5.4.0" from @prisma/client@7.5.0
npm error   node_modules/@prisma/client
npm error     dev @prisma/client@"^7.5.0" from the root project
npm error   5 more (@prisma/client-v6, prisma, prisma-v6, ts-node, valibot)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.4.6" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.4.6" 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-12T10_55_55_308Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-12T10_55_55_308Z-debug-0.log

File name: mongoose/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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.4.6
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@">=2.7" from ts-node@10.9.2
npm error   node_modules/ts-node
npm error     dev ts-node@"^10.4.0" from the root project
npm error     peerOptional ts-node@">=9.0.0" from jest-config@30.2.0
npm error     node_modules/jest-config
npm error       jest-config@"30.2.0" from @jest/core@30.2.0
npm error       node_modules/@jest/core
npm error         @jest/core@"30.2.0" from jest@30.2.0
npm error         node_modules/jest
npm error         1 more (jest-cli)
npm error       1 more (jest-cli)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error node_modules/ts-jest
npm error   dev ts-jest@"^29.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^29.0.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-12T10_55_57_804Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-12T10_55_57_804Z-debug-0.log

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 652206c5b8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep TypeScript below 6 until ts-jest supports it

This change upgrades typescript to ^6.0.0 while the adapter still uses ts-jest@^29.4.6; the existing lock metadata shows ts-jest declares typescript peer >=4.3 <6 (for example in prisma/package-lock.json line 6073). When dependencies are re-resolved (e.g., lockfile refresh or installs with stricter peer handling), this produces an unsupported toolchain that can fail install/test pipelines or Jest TypeScript transforms.

Useful? React with 👍 / 👎.

[alexolivier]

Root cause

CI failures on TS v6 are compile errors like:

src/index.test.ts(721,1): error TS2304: Cannot find name 'beforeAll'.
src/index.test.ts(791,1): error TS2593: Cannot find name 'beforeEach'. Do you need to install type definitions for a test runner?

Under TS 5, Jest globals (describe, test, expect, beforeAll, etc.) were picked up via ambient @types/jest. TS 6 tightened ambient-type discovery under moduleResolution: node16/nodenext, so the auto-include no longer resolves these globals in test files.

Proposed fix

Pick one of two approaches; option A is smaller and matches the direction Jest itself recommends.

Option A — Explicit imports in each test file (preferred)

import { describe, test, expect, beforeAll, beforeEach, afterAll } from "@jest/globals";

Files to update:

• drizzle/src/index.test.ts
• prisma/src/index.test.ts
• convex/src/*.test.ts
• mongoose/src/*.test.ts
• langchain-chromadb/src/*.test.ts

Option B — Pin ambient types in each tsconfig

Add to each adapter's tsconfig.json:

{
  "compilerOptions": {
    "types": ["jest", "node"]
  }
}

This is one-line-per-adapter but reintroduces implicit globals, which strict codebases generally avoid.

Recommendation

Land Option A as a prep PR on main (does not depend on TS 6). Once merged, rebase this PR and CI should go green without further changes. Keep #189 (Jest v30) separate since @jest/globals works identically across v29/v30.