chore(deps-dev): bump typescript from 5.9.3 to 6.0.3

[dependabot]

Bumps typescript from 5.9.3 to 6.0.3.

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

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

TypeScript 6.0

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

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• 050880c Bump version to 6.0.3 and LKG
• eeae9dd 🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...
• ad1c695 🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)
• 0725fb4 🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...
• 607a22a Bump version to 6.0.2 and LKG
• 9e72ab7 🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...
• 35ff23d 🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...
• e175b69 Bump version to 6.0.1-rc and LKG
• af4caac Update LKG
• 8efd7e8 Merge remote-tracking branch 'origin/main' into release-6.0
• Additional commits viewable in compare view

Summary by CodeRabbit

• Chores
  • Updated TypeScript development dependency from version 5.7.3 to version 6.0.3, introducing major version improvements for enhanced type checking.

[coderabbitai]

Walkthrough

Walkthrough

The typescript devDependency in package.json is bumped from ^5.7.3 to ^6.0.3. This affects the TypeScript version used by the typecheck script (tsc --noEmit).

Changes

TypeScript Dependency Bump

Layer / File(s)	Summary
TypeScript devDependency version bump package.json	The typescript entry in devDependencies is updated from ^5.7.3 to ^6.0.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating TypeScript from version 5.9.3 to 6.0.3 in devDependencies, which matches the package.json modification shown in the raw summary.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{Tip: You can configure your own custom pre-merge checks in the settings.}

Finishing Touches

Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/npm_and_yarn/typescript-6.0.3

Simplify code

• Create PR with simplified code
• Commit simplified code in branch dependabot/npm_and_yarn/typescript-6.0.3

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 27: The package.json file has been updated to specify TypeScript version
6.0.3 on line 27, but the bun.lock lockfile has not been regenerated and still
contains the old TypeScript version constraint and resolution (5.7.3/5.9.3).
Regenerate the bun.lock file by running the appropriate bun command (typically
`bun install` or `bun update`) to update the lockfile and ensure that the new
TypeScript 6.0.3 specification in package.json is properly resolved and locked
in the lockfile.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

Review info

Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 83722905-22c6-4380-a629-9cf07d480eea

Commits

Reviewing files that changed from the base of the PR and between 0a80a9c and a7502d1.

Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify package manifest vs lockfile TypeScript versions.
# Expected after refresh:
# - package.json shows ^6.0.3
# - bun.lock workspace devDependency reflects ^6.0.3
# - bun.lock resolved package is typescript@6.x

rg -n '"typescript"\s*:\s*"\^?[0-9]+\.[0-9]+\.[0-9]+"' package.json bun.lock
rg -n '"typescript": \["typescript@[0-9]+\.[0-9]+\.[0-9]+' bun.lock

Repository: four-bytes/four-opencode-git-tools

Length of output: 372

---

Lockfile out of sync — TypeScript 6.0.3 bump won't take effect until bun.lock is regenerated.

On line 27, package.json specifies "typescript": "^6.0.3", but bun.lock still declares "typescript": "^5.7.3" as a workspace devDependency and resolves to typescript@5.9.3. Package managers use the lockfile as the source of truth, so installs will continue using TypeScript 5.9.3 until the lockfile is refreshed. Regenerate bun.lock to complete this upgrade.

Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 27, The package.json file has been updated to specify
TypeScript version 6.0.3 on line 27, but the bun.lock lockfile has not been
regenerated and still contains the old TypeScript version constraint and
resolution (5.7.3/5.9.3). Regenerate the bun.lock file by running the
appropriate bun command (typically `bun install` or `bun update`) to update the
lockfile and ensure that the new TypeScript 6.0.3 specification in package.json
is properly resolved and locked in the lockfile.