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 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 (1169 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated conventional-changelog-cli@5.0.0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 1, added 0
Progress: resolved 39, reused 0, downloaded 1, added 0
Progress: resolved 195, reused 0, downloaded 1, added 0
Progress: resolved 218, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1169 entries in 9.3s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification:
  @intlify/core-base@11.4.8 was published at 2026-07-26T07:34:54.361Z, within the minimumReleaseAge cutoff (2026-07-25T13:26:29.752Z)
  @intlify/devtools-types@11.4.8 was published at 2026-07-26T07:35:00.497Z, within the minimumReleaseAge cutoff (2026-07-25T13:26:29.752Z)
  @intlify/message-compiler@11.4.8 was published at 2026-07-26T07:35:06.227Z, within the minimumReleaseAge cutoff (2026-07-25T13:26:29.752Z)
  @intlify/shared@11.4.8 was published at 2026-07-26T07:35:14.909Z, within the minimumReleaseAge cutoff (2026-07-25T13:26:29.752Z)
  vue-i18n@11.4.8 was published at 2026-07-26T07:35:18.900Z, within the minimumReleaseAge cutoff (2026-07-25T13:26:29.752Z)

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.