Bump typescript from 5.4.5 to 6.0.3 - #25
Conversation
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.4.5 to 6.0.3. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.4.5...v6.0.3) --- updated-dependencies: - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
📝 WalkthroughWalkthroughweb/package.json updates the TypeScript development dependency from version 5.4.5 to 6.0.3. ChangesTypeScript Dependency Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@web/package.json`:
- Line 20: The package.json was bumped to TypeScript 6.0.3 but the lockfile
still pins 5.4.5; regenerate the lockfile so installs actually use 6.0.3 by
running npm ci (or delete web/package-lock.json and run npm install in the web
folder) to update web/package-lock.json, then run npm run build and tsc --noEmit
to catch compile errors; also review web/tsconfig.json and
web/tsconfig.base.json for deprecated/removed compiler options introduced in TS6
and adjust (or remove) any deprecated flags so the project builds cleanly with
TypeScript 6.0.3.
🪄 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: ASSERTIVE
Plan: Pro Plus
Run ID: cae4d7a2-6364-4a80-84c8-7df5a806a1a4
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
web/package.json
| "@types/react": "18.3.3", | ||
| "@types/react-dom": "18.3.0", | ||
| "typescript": "5.4.5" | ||
| "typescript": "6.0.3" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Does TypeScript 6.0.3 exist and what are the breaking changes in TypeScript 6.0?
💡 Result:
Yes—TypeScript 6.0.3 exists. It’s published as release tag v6.0.3 in the microsoft/TypeScript repository, with a release date of 2026-04-16. [1] Breaking changes in TypeScript 6.0 (not 6.0.3 patch): 1) Transition/compat goals: TypeScript 6.0 is a bridge toward TypeScript 7.0 (native port) and introduces breaking changes and deprecations intended to be resolved before 7.0. [2][3] 2) New default deprecations behavior via tsconfig: The release notes explain that TypeScript 6.0 deprecations can be ignored by setting "ignoreDeprecations": "6.0" in tsconfig, but TypeScript 7.0 will not support any of these deprecated options. [2][3] 3) strict is now true by default: The TypeScript 6.0 RC announcement states that strict is now true by default. If you previously relied on the default false, you must explicitly set "strict": false. [4] 4) types now defaults to []: The RC announcement notes that "types" now defaults to an empty array ([]). [4] 5) Deprecations of several compiler options in 6.0: The RC announcement lists deprecated options including target: es5, moduleResolution node (node10), moduleResolution classic, --alwaysStrict false, outFile, and others (as shown in its “Deprecated:” sections). [4] If you want, paste your tsconfig.json and I’ll map which of the above are likely to affect your project specifically.
Citations:
- 1: https://github.com/microsoft/TypeScript/releases/tag/v6.0.3
- 2: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html
- 3: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
- 4: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/
🌐 Web query:
Is Next.js 16.2.6 compatible with TypeScript 6.0.3?
💡 Result:
Not fully guaranteed: Next.js 16.2.6 requires a minimum TypeScript version of 5.1.0, so TypeScript 6.0.3 should be compatible based on the minimum-version requirement. However, Next.js does not explicitly state compatibility with specific newer TypeScript patch versions (like 6.0.3) in the official docs—only that you must use at least 5.1.0. [1][2] Evidence from the official Next.js docs: - Next.js “Minimum TypeScript version: v5.1.0” in its installation/TypeScript guidance. [2] - The Next.js TypeScript configuration docs also describe TypeScript support and note errors with older TypeScript, recommending upgrading to the latest. [3] Conclusion: - Since 6.0.3 is greater than the stated minimum 5.1.0, it is expected to work with Next.js 16.2.6. [2] - If you hit any build/typecheck issues, the official guidance is to update TypeScript and related types (e.g., @types/react) to latest compatible versions. [3]
Citations:
- 1: https://github.com/vercel/next.js/blob/v16.2.1/docs/01-app/02-guides/upgrading/version-16.mdx
- 2: https://nextjs.org/docs/app/getting-started/installation
- 3: https://nextjs.org/docs/app/api-reference/config/typescript
🏁 Script executed:
#!/bin/bash
# Verify that package-lock.json contains TypeScript 6.0.3
echo "Checking package-lock.json for TypeScript version..."
if [ -f "web/package-lock.json" ]; then
jq -r '.packages."node_modules/typescript".version // .dependencies.typescript.version // "NOT FOUND"' web/package-lock.json
else
echo "package-lock.json not found in web directory"
fi
echo -e "\nChecking for TypeScript configuration files..."
fd -e json tsconfig --type fRepository: p-to-q/aleph
Length of output: 200
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== web/package.json typescript ==="
node -e 'const p=require("./web/package.json"); console.log(p.devDependencies?.typescript ?? p.dependencies?.typescript ?? "MISSING");'
echo -e "\n=== web/package-lock.json typescript resolved ==="
if [ -f "web/package-lock.json" ]; then
node - <<'NODE'
const fs=require('fs');
const lock=JSON.parse(fs.readFileSync('web/package-lock.json','utf8'));
const v = lock?.packages?.["node_modules/typescript"]?.version
?? lock?.dependencies?.typescript?.version
?? null;
console.log(v ?? "NOT FOUND");
NODE
fi
echo -e "\n=== tsconfig strict / ignoreDeprecations ==="
for f in web/tsconfig.json tsconfig.base.json; do
if [ -f "$f" ]; then
echo -e "\n--- $f ---"
rg -n '"strict"\s*:' "$f" || true
rg -n 'ignoreDeprecations' "$f" || true
rg -n 'compilerOptions' "$f" | head -n 20 || true
fi
doneRepository: p-to-q/aleph
Length of output: 351
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "=== web/package.json typescript ==="
node -e 'const p=require("./web/package.json"); console.log(p.devDependencies?.typescript ?? p.dependencies?.typescript ?? "MISSING");'
echo -e "\n=== web/package-lock.json typescript resolved ==="
if [ -f "web/package-lock.json" ]; then
node - <<'NODE'
const fs=require('fs');
const lock=JSON.parse(fs.readFileSync('web/package-lock.json','utf8'));
const v = lock?.packages?.["node_modules/typescript"]?.version
?? lock?.dependencies?.typescript?.version
?? null;
console.log(v ?? "NOT FOUND");
NODE
fi
echo -e "\n=== tsconfig strict / ignoreDeprecations ==="
for f in web/tsconfig.json tsconfig.base.json; do
if [ -f "$f" ]; then
echo -e "\n--- $f ---"
rg -n '"strict"\s*:' "$f" || true
rg -n 'ignoreDeprecations' "$f" || true
rg -n 'compilerOptions' "$f" | head -n 20 || true
fi
doneRepository: p-to-q/aleph
Length of output: 351
Fix lockfile sync: TypeScript set to 6.0.3 but lockfile still pins 5.4.5
web/package.json updates typescript to 6.0.3, but web/package-lock.json still resolves typescript to 5.4.5, so the upgrade may not actually take effect unless the lockfile is updated in this PR.
Next.js 16.2.6 should work with TS 6.0.3 (Next requires TypeScript >= 5.1.0), but TS 6.0 introduces breaking/deprecation changes—your web/tsconfig.json and tsconfig.base.json already have "strict": true, so focus on deprecated compiler options and run npm ci + npm run build/tsc --noEmit to confirm.
🤖 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 `@web/package.json` at line 20, The package.json was bumped to TypeScript 6.0.3
but the lockfile still pins 5.4.5; regenerate the lockfile so installs actually
use 6.0.3 by running npm ci (or delete web/package-lock.json and run npm install
in the web folder) to update web/package-lock.json, then run npm run build and
tsc --noEmit to catch compile errors; also review web/tsconfig.json and
web/tsconfig.base.json for deprecated/removed compiler options introduced in TS6
and adjust (or remove) any deprecated flags so the project builds cleanly with
TypeScript 6.0.3.
Bumps typescript from 5.4.5 to 6.0.3.
Release notes
Sourced from typescript's releases.
... (truncated)
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 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 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 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 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)