chore(deps): update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^6.0.3 → ^7.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v7.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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@8.67.0
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   dev typescript@"^7.0.0" from the root project
npm error   peer typescript@">=4.8.4" from ts-api-utils@2.5.0
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/type-utils@8.67.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm error     1 more (@typescript-eslint/typescript-estree)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^8.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-08-19T07_18_14_524Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-19T07_18_14_524Z-debug-0.log

[github-actions]

[HIGH] correctness
TypeScript version 7.0.0 does not exist in the public npm registry (current stable versions are ~5.x). This will cause 'npm install' or build failures.

💡 Verify the correct TypeScript version intended for the project. Revert to a valid semver range, such as '^5.6.0' (current latest stable), or ensure a custom registry is configured if this is an internal version.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — TypeScript version 7.0.0 does not exist in the public npm registry (current stable versions are ~5.x). This will cause 'npm install' or build failures.

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

[HIGH] correctness
Major version upgrade of TypeScript to 7.0.0 is likely incompatible with the current version of ts-jest (29.4.11).

💡 Verify that ts-jest and other TypeScript-dependent tooling explicitly support TypeScript 7.0.0. Upgrade ts-jest to a compatible version (e.g., v30+) or pin TypeScript to the latest compatible major version (5.x or 6.x) to prevent build failures.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — Major version upgrade of TypeScript to 7.0.0 is likely incompatible with the current version of ts-jest (29.4.11).

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

AI Code Review ✅

No issues found. LGTM!

[github-actions]

[HIGH] correctness
Upgrading typescript to a new major version (^7.0.0) introduces breaking changes and may cause immediate compilation failures. Additionally, this version may not exist in the public registry (current stable versions are ~5.x).

💡 Verify the intended version number exists. If upgrading to a major version, review the migration guide for breaking changes and ensure compatibility with the specified Node engine (>=20.0.0). Pin to a specific version (e.g., '7.0.0') without the caret (^) during the migration to prevent unexpected patch updates.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — Upgrading typescript to a new major version (^7.0.0) introduces breaking changes and may cause immediate compilation failures. Additionally, this version may not exist in the public registry (current stable versions are ~5.x).

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

AI Code Review ✅

No issues found. LGTM!

[github-actions]

[HIGH] correctness
TypeScript version ^7.0.0 does not currently exist in the public npm registry.

💡 Revert to a valid stable version (e.g., ^5.6.3) or ensure the package is available in your private registry.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — TypeScript version ^7.0.0 does not currently exist in the public npm registry.

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

[HIGH] correctness
Major version bump to typescript 7.0.0 may introduce breaking changes

💡 Review the TypeScript 7.0.0 release notes for breaking changes. Verify that the codebase and tsconfig.json are compatible with the new version, as major compiler updates often introduce stricter type checking or altered compiler options that can break the build.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — Major version bump to typescript 7.0.0 may introduce breaking changes

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

[HIGH] correctness
TypeScript version 7.0.0 does not exist in the public npm registry (current stable versions are 5.x). This will cause dependency installation to fail.

💡 Revert to the latest valid stable version, such as "typescript": "^5.6.3".

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — TypeScript version 7.0.0 does not exist in the public npm registry (current stable versions are 5.x). This will cause dependency installation to fail.

⚠️ Review blocked due to critical/high severity findings.

[github-actions]

[HIGH] correctness
TypeScript version 7.0.0 is not a valid published version in the public npm registry (current stable versions are 5.x). This will cause dependency installation to fail.

💡 Verify the intended version number (e.g., ^5.7.0) and ensure the version exists before merging.

[github-actions]

AI Code Review ❌

Found 1 finding(s):

HIGH (1)

• package.json:48 — TypeScript version 7.0.0 is not a valid published version in the public npm registry (current stable versions are 5.x). This will cause dependency installation to fail.

⚠️ Review blocked due to critical/high severity findings.