Update dependency typescript to v7 #41
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/typescript-7.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^5.8.2→^7.0.0Release Notes
microsoft/TypeScript (typescript)
v7.0.2Compare Source
v6.0.3: TypeScript 6.0.3Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Renovate Bot.
⚠️ 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:
The artifact failure details are included below:
File name: package-lock.json
Agent review — blockers
Renovate major bump
typescript^5.8.2→^7.0.0(onlypackage.json). Not merge-ready for this Nuxt/Vue app.Blockers
package.json:43— lockfile not updatedDiff touches only
package.json. Rootpackage-lock.jsonstill pinstypescript@5.9.3, sonpm ciwill not install 7.x whilepackage.jsonclaims^7.0.0. Incomplete / divergent install contract.package.json:43— TypeScript 7.0 is not viable with current Vue typecheck stackRepo runs
nuxt typecheck+vue-tsc@^3.3.7(programmatic TS API). TypeScript 7.0 ships the native compiler without a stable programmatic API; Vue language-tools / Microsoft recommend staying on the 6.x API line until ~7.1 (or a dual-install/@typescript/typescript6setup). A straighttypescript@^7here will break typecheck once the lockfile actually resolves 7.x. Prefer stay on 5.x/6.x, or a deliberate dual-toolchain change — not a bare Renovate major.Suggestions / nits
package-lock.jsonin the same PR, verifynpm run typecheck/verify, and document the dual-package alias approach if you need nativetscalongsidevue-tsc.Verdict: fail
agent/reviewuntil lockfile + tooling compatibility are addressed (or the bump is narrowed to a supported line).CI fix (attempt 1)
Root cause (Jenkins
nuxt-clients-e2e/PR-41/1):Change: regenerated
package-lock.jsonfor TypeScript 7 (a64edeb). No e2e/UI changes; snapshots not needed.Build: https://jenkins.primne.com/job/nuxt-clients-e2e/job/PR-41/1/
Agent review
Verdict: no blockers — Renovate major bump
typescript5 → 7 with lockfile sync; safe to merge from a review bar once CI/verifyis green.Blockers
None.
Suggestions / nits
typescript@7.0.2, while@nuxt/eslint-config/@nuxt/eslint-pluginnesttypescript@6.0.3so@typescript-eslint/*peers (>=4.8.4 <6.1.0) stay satisfied. Typecheck (vue-tsc/tsc) and type-aware ESLint may disagree. Prefer holding the major until@typescript-eslint/@nuxt/eslintadvertise TS 7 support, or bump those companions in the same PR.tsserverbin dropped in the TS 7 package entry (onlytscremains; native optional platform packages added). Confirm local editor tooling still works; CI scripts here usetsc/nuxt typecheck, so likely fine.package.json:43, lockfile): no app code. Rely on CI forlint+typecheck+testbefore merge.Agent review
Verdict: no blockers — Renovate major bump
typescript5 → 7 (^7.0.0→ lock7.0.2) withpackage-lock.jsonsynced; merge ofmasterinto the branch does not add app-code risk.Blockers
None.
Suggestions / nits
typescript@7.0.2, while@nuxt/eslint-config/@nuxt/eslint-pluginnesttypescript@6.0.3so@typescript-eslint/*peers (>=4.8.4 <6.1.0) stay satisfied. Typecheck (vue-tsc/tsc) and type-aware ESLint may disagree. Prefer holding the major until@typescript-eslint/@nuxt/eslintadvertise TS 7 support, or bump those companions in the same PR.tsserverbin dropped in the TS 7 package entry (onlytscremains; native optional platform packages added). Confirm local editor tooling still works; CI scripts here usetsc/nuxt typecheck, so likely fine.package.json:43, lockfile): no app / layering changes. Rely on CI forlint+typecheck+testbefore merge.agent/review
Verdict: no blockers — Renovate bump
typescript^5.8.2→^7.0.0(lock resolves to 7.0.2). Diff is onlypackage.json+package-lock.json; no app/code contract changes, no secrets.Blockers
None.
Suggestions / nits
typescript@7.0.2, while@nuxt/eslint-config/@nuxt/eslint-pluginnow nesttypescript@6.0.3because@typescript-eslint/*peers are still>=4.8.4 <6.1.0. Lint may not exercise the same compiler asnuxt typecheck/tsc. Worth watching eslint/type-aware rules after merge.vue-tsc@3.3.7peers allowtypescript >=5.0.0, so the range is formally OK, but confirm CIverify/typecheckon this SHA before merging — tooling majors can still breaknuxt typecheckor e2etscwithout lockfile drama.Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
Agent review — blockers
Renovate major bump
typescript^5.8.2→^7.0.0(lock resolves to 7.0.2). Diff is onlypackage.json+package-lock.json. Not merge-ready for this Nuxt/Vue stack.Blockers
package.json:43/ locktypescript@7.0.2— no stable Compiler API;vue-tsc/nuxt typecheckcontract brokenTypeScript 7.0 ships native
tscbut the package root export is onlylib/version.cjs(nocreateProgram/ language-service API; deferred to ~7.1). This repo’stypecheckscript isnuxt typecheck && …withvue-tsc@^3.3.7, which embeds the programmatic TS API. Microsoft’s 7.0 announcement explicitly says Vue/Volar workflows should stay on the 6.x API line (or dual-install@typescript/typescript6via npm aliases) until the API lands. A bare roottypescript@^7breaks that contract once installs resolve 7.x. Greennuxt-clients-e2edoes not coververify/typecheck(Playwright-only Jenkinsfile).Toolchain peers still reject TS 7
Nested
@typescript-eslint/*under@nuxt/eslint-config/@nuxt/eslint-pluginstill declarepeerDependencies.typescript: ">=4.8.4 <6.1.0". Lockfile papered this over with nestedtypescript@6.0.3, so ESLint andnuxt typecheckwould not even share a compiler — and the root package remains unusable for vue-tsc.Suggestions / nits
@nuxt/eslint/ typescript-eslint advertise TS 7 support, or adopt the documented dual-package alias (typescript→@typescript/typescript6, separate native 7 package fortsconly) — not a single Renovate major on roottypescript.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.