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: (in timezone UTC)

• Branch creation
  • "before 6am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 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 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.63.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@"*" from @typescript/vfs@1.6.4
npm error   node_modules/@typescript/vfs
npm error     @typescript/vfs@"^1.6.2" from @bufbuild/protoplugin@2.12.1
npm error     node_modules/@bufbuild/protoplugin
npm error       @bufbuild/protoplugin@"^2.4.0" from @protobuf-ts/plugin@2.11.1
npm error       node_modules/@protobuf-ts/plugin
npm error         @protobuf-ts/plugin@"^2.2.3-alpha.1" from @actions/artifact@6.2.1
npm error         node_modules/@actions/artifact
npm error   1 more (ts-api-utils)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.63.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^8.63.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.63.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^8.63.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-09-03T22_52_34_077Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-03T22_52_34_077Z-debug-0.log

[Copilot]

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates the project’s TypeScript dependency version in package.json.

Changes:

• Bumped typescript from ~6.0.0 to ~7.0.0

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.01%. Comparing base (ea1e02a) to head (29cf220).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
+ Coverage   89.28%   92.01%   +2.73%     
==========================================
  Files          31       12      -19     
  Lines       10711     7137    -3574     
  Branches       98        0      -98     
==========================================
- Hits         9563     6567    -2996     
+ Misses       1148      570     -578     

Flag	Coverage Δ
backend	92.01% <ø> (ø)
frontend	?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

[justanotherariel]

Let's wait until 7.1 which should provide a TS API needed for eslint. A workaround exists (running TS 6 side-by-side), but unless something requires TS 7, I would just wait for now.

[Copilot]

🔵 Needs a closer look

The lockfile is stale and the current TypeScript ESLint toolchain does not support TypeScript 7.

Review details

Suppressed comments (2)

package.json:41

• The committed lockfile still declares typescript: ~6.0.0 and resolves 6.0.3. Because the CI workflows install with npm ci, this manifest/lockfile mismatch makes dependency installation fail instead of updating the lock. Regenerate and commit package-lock.json with this bump.

    "typescript": "~7.0.0",

package.json:41

• TypeScript 7 is outside the >=4.8.4 <6.1.0 peer range of the currently locked @typescript-eslint/parser 8.63.0 (and the matching plugin packages). This leaves the lint toolchain on an unsupported compiler and can cause peer resolution or parsing failures. Upgrade the TypeScript ESLint packages to versions that explicitly support TypeScript 7, or defer this major bump.

    "typescript": "~7.0.0",

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Balanced