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

---

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)

PR PR 217 Review: TypeScript 6.0.3 → 7.0.2

Recommendation

Request Changes — The frontend build is failing (CI status: failure). A major TypeScript version bump requires Node.js >=16.20.0, but the frontend-build check failure indicates this requirement is not met by the project's current Node.js runtime.

---

Required Checks

1. Check for Breaking API Changes in Updated Dependencies

Status: VERIFIED — Breaking changes present and documented

• This PR is titled with ! marker, explicitly declaring it as a breaking change.
• TypeScript 7.x raises its minimum Node.js engine requirement from >=14.17 to >=16.20.0.
• The package-lock.json diff confirms TypeScript 7.0.2 now includes platform-specific optional dependencies (darwin-arm64, linux-x64, win32-x64, etc.) with the stricter engine constraint.

2. Run Full Test Suite After Upgrade

Status: NOT SATISFIED — frontend-build check failed

Per the authoritative CI check results:

Check	State
frontend-build	failure
test	pending
build-and-publish	pending

The frontend-build failure is the blocker. This aligns with the Node.js version mismatch: TypeScript 7.0.2 requires Node.js >=16.20.0, but the kubetix-web project pins next: "^16.0.0" (and likely runs on a Node.js version below 16.20.0 in CI).

---

Standards Compliance

• Dependency Management (AGENTS.md): Python major updates require manual review. No explicit convention covers TypeScript major updates, but the ! marker and failed build clearly warrant manual review.
• Automerge Policy (.renovaterc.json5): Python major updates are auto-merged=False. This TypeScript 7.x PR correctly disabled automerge (as shown in the PR body: "Automerge: Disabled by config").
• Breaking changes require explicit declaration and testing, which this PR attempted by disabling automerge.

---

Evidence Provider Findings

No evidence providers configured for this PR.

---

Tool Harness Findings

The tool harness ran out of budget, but the available evidence is sufficient:

• kubetix-web/package.json shows typescript: "^7.0.0" and next: "^16.0.0".
• frontend-build CI check failed, which is the concrete signal that the TypeScript upgrade breaks the build.
• GitHub releases API confirms v7.0.2 is not a published release tag in the microsoft/TypeScript repository — the most recent release is v6.0.3. The version 7.0.2 may be a pre-release, future release, or invalid reference.

---

Unknowns / Needs Verification

1. Node.js runtime version in CI: The frontend-build job likely runs on a specific Node.js version. This should be checked against the TypeScript 7.0.2 >=16.20.0 requirement.
2. TypeScript 7.0.2 release authenticity: The GitHub releases API shows no v7.0.2 tag. The PR may be referencing a non-existent or unpublished version.
3. Next.js 16.x compatibility with TypeScript 7.x: Even if Node.js 16.20.0+ is available, Next.js 16.0.0 may have its own TypeScript version constraints.

---

Findings

Severity	Category	File	Line	Message
blocker	build	kubetix-web/package.json	16	next: "^16.0.0" may require a Node.js version below TypeScript 7.0.2's required >=16.20.0; frontend-build CI check is failing
blocker	other	kubetix-web/package.json	29	TypeScript 7.0.2 does not appear in microsoft/TypeScript release tags (most recent: v6.0.3); verify this version exists and is stable before merging
minor	docs	—	—	The ! in the PR title correctly indicates breaking changes, but the change cannot merge until CI passes

[its-saffron]

🛑 Blocker: TypeScript 7.0.2 does not appear in microsoft/TypeScript release tags (most recent: v6.0.3); verify this version exists and is stable before merging

Automated finding from AI PR review.