chore: update dependency typescript to v6 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 6.0.3

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (in timezone America/Chicago)

• Branch creation
  • On day 1 of the month (* * 1 * *)
• 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: pnpm-lock.yaml

Scope: all 2 workspace projects
? Verifying lockfile against supply-chain policies (700 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 0, added 0
Progress: resolved 25, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 28, reused 0, downloaded 0, added 0
Progress: resolved 29, reused 0, downloaded 0, added 0
Progress: resolved 31, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 33, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (700 entries in 9.4s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  aws-cdk@2.1129.0 was published at 2026-07-01T13:01:46.000Z, within the minimumReleaseAge cutoff (2026-07-01T01:04:50.719Z)

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.