chore(deps): update dependency typescript to v6#132
chore(deps): update dependency typescript to v6#132red-hat-konflux[bot] wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
|
Summary by CodeRabbit
WalkthroughUpdated the TypeScript development dependency from version 5.7.2 to 6.0.0 in the package configuration file, transitioning from a minor version constraint to the next major version. Changes
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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 the current code and only fix it if needed.
Inline comments:
In `@mcp/package.json`:
- Line 47: Update the toolchain before bumping TypeScript: in package.json
upgrade ts-jest to >=29.4.7 and all `@typescript-eslint` packages to >=8.58.0
(replace the old versions referenced in package.json), then run tests and lint
to confirm compatibility; next review tsconfig.json and adjust
"moduleResolution" from "node" to "bundler" if appropriate and reconcile
"module": "commonjs" with package.json's "type": "module" (or switch module to
an ES-compatible value) to avoid resolution/runtime mismatches.
🪄 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: 9ac92eaf-84de-484c-bfc9-b90576e6ba1d
📒 Files selected for processing (1)
mcp/package.json
| "ts-jest": "^29.2.5", | ||
| "tsx": "^4.19.2", | ||
| "typescript": "^5.7.2", | ||
| "typescript": "^6.0.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Does ts-jest 29.2.5 officially support TypeScript 6.x? Please provide the official compatibility matrix or release notes link.
💡 Result:
No, ts-jest 29.2.5 does not officially support TypeScript 6.x. The peer dependency requirement is typescript >=4.3 <7, which excludes TypeScript 6.x (6.0+). TypeScript 6 support was added later in v29.4.7 on 2026-04-01 per CHANGELOG.md. Official compatibility matrix is the peer deps listed on npm: https://www.npmjs.com/package/ts-jest. Release notes for 29.2.5: https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md (bug fixes only, no TS version changes).
Citations:
- 1: https://www.npmjs.com/package/ts-jest
- 2: https://github.com/kulshekhar/ts-jest/blob/master/CHANGELOG.md
- 3: https://www.npmjs.com/package/ts-jest?activeTab=dependencies
- 4: https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md
- 5: kulshekhar/ts-jest@v29.1.2...v29.2.5
- 6: https://registry.npmjs.org/ts-jest
- 7: https://github.com/kulshekhar/ts-jest/tags
🌐 Web query:
Does typescript-eslint 8.18.2 officially support TypeScript 6.x? Please provide the official support policy/version matrix link.
💡 Result:
No, typescript-eslint 8.18.2 does not officially support TypeScript 6.x. TypeScript 6.0 was released in March 2026, while typescript-eslint 8.18.2 was released on December 23, 2024. typescript-eslint follows a policy of supporting TypeScript versions less than 2 years old, mirroring DefinitelyTyped's support window. As of v8 (including 8.18.2), the supported TypeScript range was approximately >=4.8.4 <5.8.0 or similar (up to around TS 5.6-5.8), based on historical docs and peer deps. Support for TypeScript 6.x was added later in v8.58.0 on March 30, 2026. Official support policy/version matrix: https://typescript-eslint.io/users/dependency-versions
Citations:
- 1: https://typescript-eslint.io/users/dependency-versions
- 2: https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md
- 3: https://github.com/typescript-eslint/typescript-eslint/releases
- 4: typescript-eslint/typescript-eslint@157b781
- 5: typescript-eslint/typescript-eslint@c60dbab
- 6: typescript-eslint/typescript-eslint@b2ce158
- 7: https://typescript-eslint.io/users/dependency-versions/
- 8: https://v8--typescript-eslint.netlify.app/users/dependency-versions
- 9: TypeScript 6 Support typescript-eslint/typescript-eslint#12123
🌐 Web query:
TypeScript 6.0 release notes: what breaking changes affect module resolution or CommonJS/ESM interop in Node projects?
💡 Result:
TypeScript 6.0 introduces several breaking changes and deprecations affecting module resolution and CommonJS/ESM interop in Node.js projects: 1. Deprecation of --moduleResolution node / node10: This legacy resolution mode, which modeled older Node.js behavior, is deprecated. For Node.js projects using module: commonjs, TypeScript now defaults to or allows --moduleResolution bundler, which supports modern package.json fields like exports and imports but may resolve modules differently (e.g., more permissive for CommonJS). Migrate to moduleResolution: nodenext (or node20) with matching module for strict Node.js compatibility. 2. Default moduleResolution changes to bundler: When unspecified, it now defaults to bundler for ESM-like modules, potentially altering how bare module specifiers and relative imports resolve in Node.js contexts. 3. esModuleInterop and allowSyntheticDefaultImports default to true and false values deprecated: These are now always enabled (standard emit for CJS interop), improving default import handling from CommonJS modules (resolves to module.exports) but deprecating opt-out. Explicit false settings trigger warnings; behavior changes runtime emit for default imports. 4. Deprecation of baseUrl: No longer acts as a module resolution root, affecting non-relative imports if relied upon. 5. Support for #/ subpath imports: New feature (not breaking), but combined with bundler/nodenext resolution. These prepare for TS 7.0 removals. Use "ignoreDeprecations": "6.0" temporarily. For Node.js CommonJS projects, explicitly set module: nodenext, moduleResolution: nodenext to avoid surprises.
Citations:
- 1: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html
- 2: https://truesolvers.com/articles/typescript-60-breaking-changes-what-breaks-and-what-already-helps
- 3: https://gist.github.com/privatenumber/3d2e80da28f84ee30b77d53e1693378f
- 4:
esModuleInteropandallowSyntheticDefaultImportsin TypeScript 6.0+ microsoft/TypeScript#62529 - 5: TypeScript 6.0 Iteration Plan microsoft/TypeScript#63085
- 6: https://www.sourcetrail.com/javascript/typescript-6-0-rc-features-breaking-changes-and-how-to-prepare/
- 7: Deprecate, remove
--moduleResolution node10microsoft/TypeScript#62200 - 8: Deprecate esModuleInterop and allowSyntheticDefaultImports (default to true) microsoft/TypeScript#62567
- 9: 6.0 Deprecation List microsoft/TypeScript#54500
Update ts-jest and typescript-eslint before merging TypeScript 6.0.0.
TypeScript 6.0.0 is incompatible with the current toolchain versions:
ts-jest29.2.5 requirestypescript <7, but TypeScript 6 support begins at 29.4.7+typescript-eslint8.18.2 does not support TypeScript 6 until v8.58.0+
Update both dependencies before this bump to avoid broken tests and lint failures. Additionally, TypeScript 6 deprecates --moduleResolution node in favor of bundler, which may conflict with the existing "module": "commonjs" in tsconfig.json paired with "type": "module" in package.json; validate module resolution configuration after upgrades.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@mcp/package.json` at line 47, Update the toolchain before bumping TypeScript:
in package.json upgrade ts-jest to >=29.4.7 and all `@typescript-eslint` packages
to >=8.58.0 (replace the old versions referenced in package.json), then run
tests and lint to confirm compatibility; next review tsconfig.json and adjust
"moduleResolution" from "node" to "bundler" if appropriate and reconcile
"module": "commonjs" with package.json's "type": "module" (or switch module to
an ES-compatible value) to avoid resolution/runtime mismatches.
This PR contains the following updates:
^5.7.2→^6.0.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
microsoft/TypeScript (typescript)
v6.0.3Compare Source
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
Configuration
📅 Schedule: 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.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.