deps: Update dependency typescript to v7

[renovate]

This PR contains the following updates:

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

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "after 12pm on Friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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: pnpm-lock.yaml

Scope: all 7 workspace projects
? Verifying lockfile against supply-chain policies (858 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
packages/nutils                          | [WARN] deprecated mem@10.0.0
Progress: resolved 31, reused 0, downloaded 0, added 0
Progress: resolved 36, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 0, added 0
Progress: resolved 39, reused 0, downloaded 0, added 0
Progress: resolved 40, reused 0, downloaded 0, added 0
Progress: resolved 41, reused 0, downloaded 0, added 0
Progress: resolved 42, reused 0, downloaded 0, added 0
Progress: resolved 44, reused 0, downloaded 0, added 0
[WARN] Request took 10805ms: https://registry.npmjs.org/typescript
[WARN] Request took 11131ms: https://registry.npmjs.org/@typescript-eslint%2Fparser
Progress: resolved 45, reused 0, downloaded 0, added 0
[WARN] Request took 10136ms: https://registry.npmjs.org/@typescript-eslint%2Feslint-plugin
[WARN] Request took 12404ms: https://registry.npmjs.org/@typescript-eslint%2Feslint-plugin
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 50, reused 0, downloaded 0, added 0
Progress: resolved 100, reused 0, downloaded 0, added 0
Progress: resolved 199, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (858 entries in 17.9s)
Progress: resolved 252, reused 0, downloaded 0, added 0
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  eslint@10.7.0 was published at 2026-07-10T21:22:48.956Z, within the minimumReleaseAge cutoff (2026-07-10T02:39:20.623Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.