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

[its-miso]

This PR contains the following updates:

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

---

Release Notes

microsoft/TypeScript (typescript)

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: (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 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 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 Review: TypeScript 5.9.3 → 6.0.3 Upgrade (kubetix-web)

Summary

Recommendation: Request Changes — The frontend-build CI check has failed, and the test suite is still in progress. A TypeScript major version upgrade (5.x → 6.x) introduces breaking changes that must be validated before this PR can merge.

---

Change-by-Change Findings

File	Change
kubetix-web/package.json	Updated typescript from ^5.0.0 to ^6.0.0
kubetix-web/package-lock.json	Locked TypeScript to v6.0.3

---

Required Check 1: Breaking API Changes in Updated Dependencies

Status: Breaking changes confirmed, but scope unverified due to frontend-build failure.

This is a major TypeScript version bump (5.9.3 → 6.0.3), indicated by the ! in the PR title feat(deps)!:. The compare metadata shows 178 commits ahead of v5.9.3. Key changes in the TypeScript 6.0 release include:

• Control flow container behavior for property declarations with initializers
• Package name validation renamed from NameContainsNonURISafeCharacters to NameContainsInvalidCharacters
• Stricter type checking that is typical of major TypeScript releases

The PR body explicitly links to the TypeScript 6.0 announcement blog post, acknowledging this is a significant release. However, the frontend-build failure indicates that the existing codebase contains code that is incompatible with TypeScript 6.x.

---

Required Check 2: Run Full Test Suite After Upgrade

Status: NOT PASSED — frontend-build has FAILED; test suite is still in progress.

The CI check results are authoritative:

Check	Status
frontend-build	❌ FAILED
test	⏳ in_progress
lint	✅ completed
helm-check	✅ completed
security	✅ completed
legacy-test	✅ completed
build-and-publish	⏳ in_progress
e2e-tests	⏳ queued

The frontend-build failure is a blocker. This check runs next build (or equivalent) which compiles the Next.js application including TypeScript compilation. A failure here means the existing TypeScript code in kubetix-web/ has type errors that are incompatible with TypeScript 6.x's stricter checking.

---

Standards Compliance

Per AGENTS.md → Dependency Management → Automerge Policy:

| Python major | ❌ No | Requires manual review |

While this policy explicitly covers Python major updates, the same conservative principle applies here: TypeScript major updates require manual review and must pass all CI checks before merge. The ! in the PR title correctly signals this is a breaking change requiring manual intervention.

The PR has automerge disabled by config, which is correct and expected behavior for a major version bump.

---

Linked Issue Fit

No linked issues found in the PR body.

---

Unknowns / Needs Verification

1. Root cause of frontend-build failure: The CI did not provide detailed error output in this corpus. The failure is likely due to TypeScript 6.x type errors in the kubetix-web/ codebase. The actual compiler errors need to be examined.

2. Test suite final result: The test check is still in progress. The final result is not yet available.

3. TypeScript 6.0 breaking changes scope: While the upstream TypeScript changelog mentions significant changes (178 commits), the specific breaking changes affecting this codebase's type definitions and patterns are not enumerated in the available corpus.

---

Action Required

This PR cannot be approved in its current state:

1. Fix the frontend-build failure — Investigate and resolve the TypeScript compilation errors introduced by the 5.x → 6.x upgrade. Common causes include stricter null/undefined checking, changed inference behavior, or removed deprecated type aliases.

2. Wait for test check completion — Ensure the full test suite passes before requesting re-review.

3. Revisit after fixes — Once frontend-build and test both pass, re-request review to confirm the breaking changes have been addressed.

[its-saffron]

🛑 Blocker: frontend-build CI check failed — the TypeScript 6.x upgrade introduced type errors that must be resolved before merge. Check the CI logs for the specific compilation errors.

Automated finding from AI PR review.

[its-saffron]

⚠️ Major: test CI check is still in progress — the full test suite has not completed. This PR cannot be approved until all CI checks pass.

Automated finding from AI PR review.