chore(deps)(deps-dev): bump typescript from 5.9.3 to 6.0.3#87
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
Warning
|
| Layer / File(s) | Summary |
|---|---|
Dependency Version package.json |
TypeScript devDependencies entry bumped from ^5.5.3 to ^6.0.3. |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Eu pulo nas teclas com um brilho no olhar,
Um bump no TypeScript faz os tipos dançar,
Compilador novo, passos a rimar,
Eu roio um bug e deixo o build cantar,
Coelhinho feliz vê o código alinhar.
🚥 Pre-merge checks | ✅ 3 | ❌ 2
❌ Failed checks (2 warnings)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Title check | O título refere-se a uma versão diferente (5.9.3) da que está no sumário (5.5.3), criando imprecisão e potencial confusão. | Atualize o título para refletir a versão correta: 'chore(deps)(deps-dev): bump typescript from 5.5.3 to 6.0.3' ou verifique qual versão anterior é a correta. | |
| Description check | A descrição não segue o template obrigatório do repositório, faltam seções críticas como Descrição, Tipo de mudança, Checklist de validação e Como testar. | Preencha o template completo com: descrição breve, tipo de mudança (Chore), checklist de validação (incluindo 'npx tsc --noEmit'), passos para testar e notas do review. |
✅ Passed checks (3 passed)
| Check name | Status | Explanation |
|---|---|---|
| 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.
Comment @coderabbitai help to get the list of available commands and usage tips.
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/typescript-6.0.3
branch
from
55a0183 to
4eb3da0
Compare
![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 `@package.json`:
- Line 178: The package.json currently pins "typescript": "^6.0.3" which is
incompatible with the installed `@typescript-eslint` v8.18.0; update package.json
to fix the mismatch by either upgrading both `@typescript-eslint/parser` and
`@typescript-eslint/eslint-plugin` to >=8.58.0 (recommended) or by downgrading
"typescript" to a supported ^5.x (e.g., ^5.4); ensure you update the
corresponding devDependencies entries for "@typescript-eslint/parser" and
"@typescript-eslint/eslint-plugin" when choosing the upgrade path and run
npm/yarn install and your lint/typecheck scripts to verify.
🪄 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: e70c765c-9cd4-40d1-bb89-8a0461bd41d1
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "tailwindcss": "^3.4.19", | ||
| "tailwindcss-animate": "^1.0.7", | ||
| "typescript": "^5.5.3", | ||
| "typescript": "^6.0.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
For @typescript-eslint/parser8.18.0 and@typescript-eslint/eslint-plugin 8.18.0, what TypeScript versions are officially supported? Does the support range include TypeScript 6.0.x?
💡 Result:
For @typescript-eslint/parser 8.18.0 and @typescript-eslint/eslint-plugin 8.18.0, the officially supported TypeScript versions are >=4.8.4 and <5.8.0.[1][2] This is indicated by the peer dependency range in the parser's package.json ("typescript": ">=4.8.4 <5.8.0"), which the plugin shares via shared internals like @typescript-eslint/typescript-estree.[3][4] The parser warns on unsupported versions, with examples showing ranges like >=4.7.4 <5.7.0 in nearby versions, confirming the pattern of supporting recent TS versions (less than 2 years old).[3][4] TypeScript 6.0.x is not supported, as it exceeds the upper bound <5.8.0; support for TS 6 was added later in v8.58.0.[5][6]
Citations:
- 1: typescript-eslint/typescript-eslint@b2ce158
- 2: typescript-eslint/typescript-eslint@157b781
- 3: https://typescript-eslint.io/packages/parser
- 4: https://typescript-eslint.io/users/dependency-versions
- 5: https://github.com/typescript-eslint/typescript-eslint/blob/main/CHANGELOG.md
- 6: https://npmx.dev/package/@typescript-eslint/parser/v/8.58.0
🌐 Web query:
Does Vite 5.4.19 (and @vitejs/plugin-react-swc 3.11.0) officially support TypeScript 6.0.x in type-checking and development workflows?
💡 Result:
No—there is no official statement from Vite 5.4.19 or @vitejs/plugin-react-swc 3.11.0 that they “support TypeScript 6.0.x” specifically for type-checking and development workflows. Why: 1) Vite itself does not perform TypeScript type checking; it only transpiles TypeScript files, and it explicitly notes that type checking is handled by your IDE/build process, not by Vite. So any “type-checking support” is not something Vite claims for any particular TypeScript version (including 6.0.x) [1]. 2) The official Vite plugin page for TypeScript behavior indicates transpilation-only behavior and discusses tsconfig handling, but it does not claim compatibility guarantees with a specific TypeScript major/minor range [1]. 3) The official @vitejs/plugin-react-swc documentation we found describes behavior/limits (e.g., tsconfig not resolved; target ignored and defaults used), but we did not find any official peer dependency or stated TypeScript version range that explicitly includes TypeScript 6.0.x [2]. What we can confirm from authoritative sources we found: - Vite 5.4.19 exists as a release (but the release notes/changelog we saw are about other fixes, not TypeScript 6 compatibility) [3][4]. - The Vite core repository later includes an internal/template change upgrading TypeScript to 6 (commit/issues from 2026-04), which suggests ecosystem movement toward TS 6, but it is not an explicit claim that Vite 5.4.19 (or plugin 3.11.0) officially supports TS 6.0.x in the specific way you asked [5][6]. Conclusion: Based on the official docs we located, Vite 5.4.19 and @vitejs/plugin-react-swc 3.11.0 do not “officially support TypeScript 6.0.x in type-checking workflows” (because Vite doesn’t do type checking) and we also did not find an official compatibility guarantee specifically naming TS 6.0.x for those versions [1][2]. If you want, tell me whether your workflow uses (a) IDE-only type checking (tsserver), (b) tsc --noEmit, (c) vite type-checking via a separate tool (e.g., vue-tsc / eslint), or (d) testing tools, and I can research which part of the toolchain needs TS 6 support.
Citations:
- 1: https://vite.dev/guide/features
- 2: https://www.npmjs.com/package/@vitejs/plugin-react-swc
- 3: https://github.com/vitejs/vite/blob/v5.4.19/packages/vite/CHANGELOG.md
- 4: vitejs/vite@80a333a
- 5: vitejs/vite@cc41398
- 6: refactor: upgrade to typescript 6 vitejs/vite#22110
@typescript-eslint 8.18.0 does not support TypeScript 6.0.3—upgrade to 8.58.0+ or downgrade TypeScript.
TypeScript 6.0.3 requires @typescript-eslint/parser and @typescript-eslint/eslint-plugin v8.58.0 or later. The pinned version 8.18.0 only supports TypeScript >=4.8.4 <5.8.0, which excludes TS 6.0.x. Since your lint and typecheck scripts both run tsc --noEmit, this incompatibility will cause failures. Either upgrade both ESLint-TypeScript packages to ^8.58.0+ or pin TypeScript to ^5.4 instead.
🤖 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 178, The package.json currently pins "typescript":
"^6.0.3" which is incompatible with the installed `@typescript-eslint` v8.18.0;
update package.json to fix the mismatch by either upgrading both
`@typescript-eslint/parser` and `@typescript-eslint/eslint-plugin` to >=8.58.0
(recommended) or by downgrading "typescript" to a supported ^5.x (e.g., ^5.4);
ensure you update the corresponding devDependencies entries for
"@typescript-eslint/parser" and "@typescript-eslint/eslint-plugin" when choosing
the upgrade path and run npm/yarn install and your lint/typecheck scripts to
verify.
4eb3da0 to
f8d4c32
Compare
|
@coderabbitai full review Generated by Claude Code |
|
Tip For best results, initiate chat on the files or code changes.
|
| Area | Change |
|---|---|
target |
target: es5 is now deprecated — you'll need to migrate to a newer target or use an external compiler. |
moduleResolution |
moduleResolution: classic has been removed entirely. All practical use cases are now served by nodenext or bundler. |
esModuleInterop |
esModuleInterop and allowSyntheticDefaultImports can no longer be set to false. The safer interop behavior is now always enabled. |
downlevelIteration |
Setting --downlevelIteration at all will now lead to a deprecation error. |
strict |
If you never had "strict": true in your tsconfig and relied on the old default of false, you may get a wall of new errors. |
types |
TypeScript previously auto-included every @types/* package in node_modules. Now types defaults to []. You'll need to add "types": ["node"] (or whatever packages you need) explicitly. |
moduleResolution silent shift |
Projects using --module commonjs without explicit moduleResolution now get bundler instead of node10. |
"use strict" emission |
TypeScript will now unconditionally emit "use strict" in non-ESM files. ESM files are already strict by spec, so this only affects CommonJS output. |
✅ Recommendations
- Run the automated migration tool before or after merging:
npx@andrewbranch/ts5to6`` — this tool handles the two most disruptive changes (baseUrl removal and rootDir inference) automatically. - Run a dry type-check:
npx tsc --noEmitto surface any new errors introduced by the bump. - Review your
tsconfig.jsonagainst the changes above, particularlytarget,moduleResolution, andtypes.
💡 If you have an explicit
tsconfig.jsonthat setsstrict,module,target, andtypesexplicitly, you probably won't see many issues.
Triggering a full review of the PR now.
[full_review]
User requested a full review of PR #87 (TypeScript 5.8.3 → 6.0.3 bump).
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/typescript-6.0.3
branch
from
f8d4c32 to
e4b9c26
Compare
|
🔴 Parecer técnico — SEGURAR. NÃO mergear sem teste extensivo Tipo: Linguagem major (5.8.3 → 6.0.3) TypeScript 6.0 é uma release nova. Apesar do TS ter histórico de transições suaves, sempre há:
Para o PromoGifts especificamente:
Recomendação: fechar este PR como will not adopt now e configurar Dependabot pra ignorar majors de TypeScript: # .github/dependabot.yml
ignore:
- dependency-name: typescript
update-types: [version-update:semver-major]Reabrir manualmente quando time decidir migrar (provavelmente Q3/Q4 2026 após Fase 1-3 da auditoria fecharem). — Claude (housekeeping de PRs, 08/05/2026) |
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/typescript-6.0.3
branch
from
e4b9c26 to
52cfb10
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@dependabot rebase |
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 6.0.3. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...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
force-pushed
the
dependabot/npm_and_yarn/typescript-6.0.3
branch
from
52cfb10 to
1b2706e
Compare
1 participant
Bumps typescript from 5.9.3 to 6.0.3.
Release notes
Sourced from typescript's releases.
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.0Summary by CodeRabbit
Notas de Lançamento