chore(deps): update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^6.0.0 → ^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: .github/actions/core/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.12
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
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <7" from ts-jest@29.4.12
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@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <7" from ts-jest@29.4.12
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-08-14T20_49_47_538Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-14T20_49_47_538Z-debug-0.log

[ricogu]

build-test-core is failing — TypeScript 7 is not yet supported by our test toolchain

I looked into the failing build-test-core check. There are two layers to it:

1. Surface error (lockfile out of sync)
package.json was bumped to typescript@^7.0.0 but package-lock.json still pins typescript@6.0.3, so npm ci fails:

npm error `npm ci` can only install packages when your package.json and package-lock.json are in sync.
npm error Invalid: lock file's typescript@6.0.3 does not satisfy typescript@7.0.2

2. The real blocker (ts-jest does not support TS 7)
Regenerating the lockfile does not fix it. TypeScript 7.0 is the new native ("tsgo") compiler generation, and our test runner ts-jest is incompatible with it:

• ts-jest@29.4.11 (latest) declares peer typescript: ">=4.3 <7", so npm ci then hard-fails with ERESOLVE.
• Even bypassing the peer check, npm test crashes because ts-jest cannot consume the TS 7 compiler API:

  TypeError: Cannot read properties of undefined (reading 'readFile')
      at ConfigSet._resolveTsConfig (node_modules/ts-jest/.../config-set.js)
  

• npm view ts-jest peerDependencies confirms no released ts-jest version (latest 29.4.11, next 29.0.0-next.1) allows typescript >=7.

Good news: the source itself is TS 7-ready — tsc (7.0.2) compiles it cleanly (exit 0). The only blocker is the Jest transformer.

Recommendation: hold this bump until ts-jest publishes TypeScript 7 support. Migrating off ts-jest (to swc/babel/vitest) purely to satisfy this Renovate bump would be unjustified test-infra risk (ESM handling, path resolution, @actions/core mocks, diagnostics). Once npm view ts-jest peerDependencies allows typescript >=7 and a local npm ci && npm test && npm run build passes without peer overrides, this can be taken as a normal dependency update.