Skip to content

chore(deps): update dependency typescript to v6#351

Open
smartway-bot[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-6.x
Open

chore(deps): update dependency typescript to v6#351
smartway-bot[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-6.x

Conversation

@smartway-bot
Copy link
Copy Markdown
Contributor

@smartway-bot smartway-bot Bot commented Apr 6, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typescript (source) ^5.2.2 -> ^6.0.0 age adoption passing confidence

Release Notes

microsoft/TypeScript (typescript)

v6.0.3: TypeScript 6.0.3

Compare Source

For release notes, check out the release announcement blog post.

Downloads are available on:

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

Downloads are available on:

v5.9.3: TypeScript 5.9.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

Downloads are available on:

v5.9.2: TypeScript 5.9

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

Downloads are available on:

v5.8.3: TypeScript 5.8.3

Compare Source

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement.

Downloads are available on:

v5.8.2: TypeScript 5.8

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

v5.6.3: TypeScript 5.6.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.6.2: TypeScript 5.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.4: TypeScript 5.5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.3: TypeScript 5.5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.5.2: TypeScript 5.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.5: TypeScript 5.4.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.3: TypeScript 5.4.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.4.2: TypeScript 5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.3.3: TypeScript 5.3.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.3.2: TypeScript 5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 06:59 AM, only on Monday ( * 0-6 * * 1 ) (UTC), 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 Renovate Bot.

@smartway-bot smartway-bot Bot added the dependencies Pull requests that update a dependency file label Apr 6, 2026
@smartway-bot
Copy link
Copy Markdown
Contributor Author

smartway-bot Bot commented Apr 6, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: ts-jest@29.1.1
npm ERR! Found: typescript@6.0.3
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"^6.0.0" from the root project
npm ERR!   peer typescript@">=3.9" from eslint-config-standard-with-typescript@19.0.1
npm ERR!   node_modules/eslint-config-standard-with-typescript
npm ERR!     dev eslint-config-standard-with-typescript@"19.0.1" from the root project
npm ERR!   3 more (ts-api-utils, ts-node, tsutils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.3 <6" from ts-jest@29.1.1
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.1.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@5.9.3
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=4.3 <6" from ts-jest@29.1.1
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"^29.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2026-04-24T00_00_35_813Z-debug-0.log

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 6, 2026

📝 Walkthrough

Walkthrough

TypeScript development dependency updated from version 5.2.2 to 6.0.0 in package.json. This change updates the TypeScript compiler used for type-checking workflows within the project.

Changes

Cohort / File(s) Summary
TypeScript Dependency Update
package.json
TypeScript development dependency upgraded from ^5.2.2 to ^6.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • jonperron

Poem

🐰 TypeScript hops from five to six,
Our types now type with modern tricks,
A version bump so clean and bright,
The rabbit cheers—the future's right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(deps): update dependency typescript to v6' directly and accurately summarizes the main change—updating the TypeScript dependency to version 6.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 renovate/typescript-6.x

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

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 6, 2026

🛡️ The security scan result : Repo and Config

@smartway-bot smartway-bot Bot force-pushed the renovate/typescript-6.x branch from 6735d3a to 54d9d17 Compare April 24, 2026 00:00
@smartway-bot smartway-bot Bot requested a review from a team as a code owner April 24, 2026 00:00
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 68: package-lock.json is out of sync with the updated TypeScript entry in
package.json; run npm install locally to update/regenerate package-lock.json so
the lockfile matches the new "typescript": "^6.0.0" entry, verify the updated
package-lock.json is added to the commit, and push the commit so the CI pipeline
can pass; reference the package.json "typescript" field and the
package-lock.json file when making this change.
- Line 68: The package.json currently pins "typescript": "^6.0.0" which is
incompatible with ts-jest@29.1.0 (peer <6); update dependencies to resolve this
by either (A) upgrading ts-jest to a version that declares support for
TypeScript 6 (change ts-jest from "ts-jest@29.1.0" to a newer compatible
release) or (B) downgrading the "typescript" entry to a <6.x range (e.g.,
"^5.x") so it satisfies ts-jest@29.1.0; modify package.json accordingly and run
install/test to verify (focus on the "typescript" and "ts-jest" dependency
entries).
- Line 68: Upgrade guidance: Because package.json now pins "typescript":
"^6.0.0", update tsconfig.json to explicitly set rootDir (e.g., "rootDir": "src"
if your sources live there), add required types (e.g., "types": ["node"]), raise
the target to a modern ES (e.g., "target": "es2015" or later) and change
moduleResolution to a supported scheme ("bundler" or "nodenext"); optionally add
"ignoreDeprecations": "6.0" to suppress temporary warnings. Locate and modify
the tsconfig.json compilerOptions keys rootDir, types, target, moduleResolution,
and add ignoreDeprecations as needed.
🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 773dd94e-873e-4eda-aea8-614fb2651d77

📥 Commits

Reviewing files that changed from the base of the PR and between 55da96a and 54d9d17.

📒 Files selected for processing (1)
  • package.json

Comment thread package.json
"ts-jest": "^29.1.0",
"ts-node": "^10.9.2",
"typescript": "^5.2.2"
"typescript": "^6.0.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Pipeline failure: Regenerate package-lock.json.

The CI pipeline failed because package-lock.json is out of sync with the updated TypeScript version in package.json. After verifying compatibility (see other comments), run npm install to regenerate the lockfile.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 68, package-lock.json is out of sync with the updated
TypeScript entry in package.json; run npm install locally to update/regenerate
package-lock.json so the lockfile matches the new "typescript": "^6.0.0" entry,
verify the updated package-lock.json is added to the commit, and push the commit
so the CI pipeline can pass; reference the package.json "typescript" field and
the package-lock.json file when making this change.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for TypeScript version constraints in ecosystem dependencies

echo "=== Checking peerDependencies of TypeScript ecosystem tools ==="

# Check `@typescript-eslint/eslint-plugin` peer deps
echo -e "\n@typescript-eslint/eslint-plugin@7.9.0:"
npm view `@typescript-eslint/eslint-plugin`@7.9.0 peerDependencies.typescript

# Check ts-jest peer deps
echo -e "\nts-jest@29.1.0:"
npm view ts-jest@29.1.0 peerDependencies.typescript

# Check ts-node peer deps  
echo -e "\nts-node@10.9.2:"
npm view ts-node@10.9.2 peerDependencies.typescript

# Check eslint-config-standard-with-typescript peer deps
echo -e "\neslint-config-standard-with-typescript@19.0.1:"
npm view eslint-config-standard-with-typescript@19.0.1 peerDependencies

Repository: ZeroGachis/smartway-react-native-ui

Length of output: 526


Resolve TypeScript 6.0 incompatibility with ts-jest.

ts-jest@29.1.0 does not support TypeScript 6.0—its peer dependency constraint is >=4.3 <6. Either upgrade to a newer version of ts-jest that supports TypeScript 6.0, or use a TypeScript version below 6.0. The other tools (ts-node@10.9.2, eslint-config-standard-with-typescript@19.0.1, and @typescript-eslint/eslint-plugin@7.9.0) are compatible with TypeScript 6.0.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 68, The package.json currently pins "typescript":
"^6.0.0" which is incompatible with ts-jest@29.1.0 (peer <6); update
dependencies to resolve this by either (A) upgrading ts-jest to a version that
declares support for TypeScript 6 (change ts-jest from "ts-jest@29.1.0" to a
newer compatible release) or (B) downgrading the "typescript" entry to a <6.x
range (e.g., "^5.x") so it satisfies ts-jest@29.1.0; modify package.json
accordingly and run install/test to verify (focus on the "typescript" and
"ts-jest" dependency entries).

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

TypeScript 6.0.0 release notes breaking changes

💡 Result:

TypeScript 6.0.0 introduces several breaking changes and deprecations as a transition release preparing for TypeScript 7.0 (native Go-based compiler). It maintains API compatibility with 5.9 but changes defaults and deprecates legacy options. Key breaking changes and default shifts: - rootDir defaults to . (tsconfig directory) instead of inferred from sources. Set explicitly if sources are in subdirs like src/. - types defaults to [] (no auto-inclusion of @types packages). Explicitly list needed types (e.g., ["node"]) for build performance gains (20-50%). - Deprecated target: es5 (lowest now es2015/es2025 recommended). - Deprecated --downlevelIteration. - Deprecated --moduleResolution node/node10 (migrate to nodenext or bundler) and classic (removed). - Deprecated --baseUrl (use paths mappings without it). - Deprecated --esModuleInterop false / --allowSyntheticDefaultImports false. - Deprecated --alwaysStrict false (strict mode closer to default). - Deprecated outFile. - Deprecated legacy module syntax for namespaces, import asserts {}, no-default-lib directives. - Specifying CLI files with existing tsconfig.json now errors. - Behavioral: strict/use strict closer to always on; moduleResolution bundler with commonjs; type ordering may differ (use --stableTypeOrdering flag). Deprecations can be ignored in 6.0 via "ignoreDeprecations": "6.0" in tsconfig.json but will be removed in 7.0. Address warnings before upgrading further. Official docs recommend explicit tsconfig settings reflecting modern practices (target es2025, bundler resolution, explicit types). For full details, see official handbook: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html

Citations:


Update tsconfig.json for TypeScript 6.0.0 breaking changes.

TypeScript 6.0.0 introduces significant defaults changes and deprecations:

  • rootDir now defaults to . (tsconfig directory) instead of being inferred; set explicitly if sources are in subdirectories like src/
  • types now defaults to [] (no auto-inclusion of @types packages); explicitly list required types like ["node"]
  • Deprecated: target: es5 (use es2015 or later), --moduleResolution node/classic (migrate to bundler or nodenext), --baseUrl, --esModuleInterop false, --allowSyntheticDefaultImports false

Update tsconfig.json with explicit settings for rootDir, types, target, and moduleResolution to align with modern practices. Deprecation warnings can be suppressed temporarily with "ignoreDeprecations": "6.0" but will be removed in TypeScript 7.0.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 68, Upgrade guidance: Because package.json now pins
"typescript": "^6.0.0", update tsconfig.json to explicitly set rootDir (e.g.,
"rootDir": "src" if your sources live there), add required types (e.g., "types":
["node"]), raise the target to a modern ES (e.g., "target": "es2015" or later)
and change moduleResolution to a supported scheme ("bundler" or "nodenext");
optionally add "ignoreDeprecations": "6.0" to suppress temporary warnings.
Locate and modify the tsconfig.json compilerOptions keys rootDir, types, target,
moduleResolution, and add ignoreDeprecations as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants