feat(deps)!: Update dependency typescript (6.0.3 → 7.0.2)

[its-miso]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	^6.0.0 → ^7.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (in timezone America/Edmonton)

• 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 has been generated by Mend Renovate.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_request_changes,fast_low_confidence)

Review Summary

Recommendation: Request Changes

This PR proposes upgrading TypeScript from 6.0.3 to 7.0.2. While the change appears mechanically correct in package.json and package-lock.json, there are critical blocking issues that prevent approval.

---

Required Check Results

1. Check for Breaking API Changes in Updated Dependencies

Status: ⚠️ UNVERIFIABLE

The PR title includes the ! modifier indicating breaking changes (feat(deps)!:), but the upgrade cannot be validated:

• Version existence: The GitHub Releases API for microsoft/TypeScript shows the latest available release is v6.0.3 (published 2026-04-16). No v7.0.2 tag exists in the official repository. The Renovate bot's release notes reference a compare link, but the release data itself was not retrievable.
• Breaking changes: Without a confirmed, published v7.0.2 release, the nature and scope of breaking changes cannot be assessed. TypeScript major version upgrades typically include stricter type checking, removed deprecated APIs, and language feature changes.
• Source: GitHub Releases API (repos/microsoft/TypeScript/releases) returned only versions up to v6.0.3.

This upgrade references a non-existent TypeScript version and cannot be approved until the target version is confirmed published and breaking changes are documented.

2. Run Full Test Suite After Upgrade

Status: ❌ NOT PASSED — CI Failures

The CI check results show:

• Build: failure
• Lint: failure
• Typecheck: success
• Tests: pending
• Docker Build: pending

The Build and Lint stages have failed, blocking the PR. The full test suite has not yet run. This PR cannot be merged until CI passes.

---

Standards Compliance

Standard	Status	Notes
Repository conventions	⚠️ Partial	Mechanical change correct (package.json + lockfile), but targets unverified version
CI requirements	❌ Failed	Build and Lint failures must be resolved
Semantic versioning	⚠️ Major version bump with ! marker	Correctly signals breaking changes

---

Evidence Provider Findings

• GitHub Releases Enrichment (microsoft/TypeScript): No v7.0.2 tag found. Latest release is v6.0.3 (2026-04-16). This raises a significant concern about whether the target version exists or is published yet.
• CI Status API: Build and Lint checks failed on commit 50b0fede60e7c32094cbac196b8294ebf05625d0.

---

Tool Harness Findings

• Fetching https://github.com/microsoft/TypeScript/releases/tag/v7.0.0: 404 Not Found
• Fetching https://registry.npmjs.org/typescript: Host not allowlisted
• GitHub releases API: Success, but v7.0.2 tag absent from response

---

Unknowns / Needs Verification

1. Does TypeScript v7.0.2 exist? The GitHub API shows no such release. This may indicate a pre-release, a misconfiguration by Renovate, or a version that doesn't exist.
2. What are the breaking changes? Without a confirmed version, no changelog or breaking change analysis is possible.
3. Why did Build and Lint fail? The failure details are not included in the corpus; investigation required.

---

Action Required Before Approval

1. Verify TypeScript v7.0.2 is a real, published version from the official Microsoft/TypeScript repository
2. Fix CI failures — resolve Build and Lint failures, then ensure Tests pass
3. Document breaking changes — if the version is valid, enumerate the breaking changes and confirm the codebase is compatible

[its-saffron]

🛑 Blocker (bug): TypeScript v7.0.2 does not appear to exist in the official microsoft/TypeScript repository. The GitHub Releases API confirms only v6.0.3 as the latest release. This PR cannot be approved until the target version is verified.

Automated finding from AI PR review.