chore(deps): update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 7.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

v6.0.3: TypeScript 6.0.3

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

---

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

? Verifying lockfile against supply-chain policies (1352 entries)...
✗ Lockfile failed supply-chain policy check (1352 entries in 8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 14 lockfile entries failed verification:
  @changesets/apply-release-plan@8.0.0 was published at 2026-08-11T12:06:15.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/assemble-release-plan@7.0.0 was published at 2026-08-11T12:06:11.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/changelog-git@1.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/cli@3.0.0 was published at 2026-08-11T12:06:20.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/config@4.0.0 was published at 2026-08-11T12:06:11.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/errors@1.0.0 was published at 2026-08-11T12:06:01.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/get-dependents-graph@3.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/git@4.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/parse@1.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/pre@3.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/read@1.0.0 was published at 2026-08-11T12:06:11.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/should-skip-package@1.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/types@7.0.0 was published at 2026-08-11T12:06:01.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)
  @changesets/write@1.0.0 was published at 2026-08-11T12:06:06.000Z, within the minimumReleaseAge cutoff (2026-08-11T03:06:08.762Z)

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.