Skip to content

chore(deps): update dependency typescript to v7 - #26

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

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

Conversation

@renovate

@renovate renovate Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^6.0.3^7.0.2 age confidence

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • "after 10am and before 4pm every weekday"

🚦 Automerge: Disabled because a matching PR was automerged previously.

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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from nsheaps August 12, 2026 03:10
@renovate

renovate Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/eslint-plugin@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn node_modules/@typescript-eslint/eslint-plugin
npm warn   @typescript-eslint/eslint-plugin@"8.67.0" from typescript-eslint@8.67.0
npm warn   node_modules/typescript-eslint
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn     @typescript-eslint/eslint-plugin@"8.67.0" from typescript-eslint@8.67.0
npm warn     node_modules/typescript-eslint
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/parser@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/parser@8.67.0
npm warn node_modules/@typescript-eslint/parser
npm warn   peer @typescript-eslint/parser@"^8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn   1 more (typescript-eslint)
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/parser@8.67.0
npm warn   node_modules/@typescript-eslint/parser
npm warn     peer @typescript-eslint/parser@"^8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn     1 more (typescript-eslint)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/project-service@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/project-service@8.67.0
npm warn node_modules/@typescript-eslint/project-service
npm warn   @typescript-eslint/project-service@"8.67.0" from @typescript-eslint/typescript-estree@8.67.0
npm warn   node_modules/@typescript-eslint/typescript-estree
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/project-service@8.67.0
npm warn   node_modules/@typescript-eslint/project-service
npm warn     @typescript-eslint/project-service@"8.67.0" from @typescript-eslint/typescript-estree@8.67.0
npm warn     node_modules/@typescript-eslint/typescript-estree
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/tsconfig-utils@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/tsconfig-utils@8.67.0
npm warn node_modules/@typescript-eslint/tsconfig-utils
npm warn   @typescript-eslint/tsconfig-utils@"^8.67.0" from @typescript-eslint/project-service@8.67.0
npm warn   node_modules/@typescript-eslint/project-service
npm warn   1 more (@typescript-eslint/typescript-estree)
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/tsconfig-utils@8.67.0
npm warn   node_modules/@typescript-eslint/tsconfig-utils
npm warn     @typescript-eslint/tsconfig-utils@"^8.67.0" from @typescript-eslint/project-service@8.67.0
npm warn     node_modules/@typescript-eslint/project-service
npm warn     1 more (@typescript-eslint/typescript-estree)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/type-utils@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/type-utils@8.67.0
npm warn node_modules/@typescript-eslint/type-utils
npm warn   @typescript-eslint/type-utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/type-utils@8.67.0
npm warn   node_modules/@typescript-eslint/type-utils
npm warn     @typescript-eslint/type-utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/typescript-estree@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/typescript-estree@8.67.0
npm warn node_modules/@typescript-eslint/typescript-estree
npm warn   @typescript-eslint/typescript-estree@"8.67.0" from @typescript-eslint/parser@8.67.0
npm warn   node_modules/@typescript-eslint/parser
npm warn   3 more (@typescript-eslint/type-utils, ...)
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/typescript-estree@8.67.0
npm warn   node_modules/@typescript-eslint/typescript-estree
npm warn     @typescript-eslint/typescript-estree@"8.67.0" from @typescript-eslint/parser@8.67.0
npm warn     node_modules/@typescript-eslint/parser
npm warn     3 more (@typescript-eslint/type-utils, ...)
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/utils@8.67.0
npm warn Found: typescript@7.0.2
npm warn node_modules/typescript
npm warn   dev typescript@"^7.0.2" from the root project
npm warn   1 more (ts-api-utils)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/utils@8.67.0
npm warn node_modules/@typescript-eslint/utils
npm warn   @typescript-eslint/utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn   2 more (@typescript-eslint/type-utils, typescript-eslint)
npm warn
npm warn Conflicting peer dependency: typescript@6.0.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/utils@8.67.0
npm warn   node_modules/@typescript-eslint/utils
npm warn     @typescript-eslint/utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm warn     node_modules/@typescript-eslint/eslint-plugin
npm warn     2 more (@typescript-eslint/type-utils, typescript-eslint)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: typescript-eslint@8.67.0
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   dev typescript@"^7.0.2" from the root project
npm error   peer typescript@">=4.8.4" from ts-api-utils@2.5.0
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       @typescript-eslint/eslint-plugin@"8.67.0" from typescript-eslint@8.67.0
npm error       node_modules/typescript-eslint
npm error         dev typescript-eslint@"^8.67.0" from the root project
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/type-utils@8.67.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"8.67.0" from @typescript-eslint/eslint-plugin@8.67.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"8.67.0" from typescript-eslint@8.67.0
npm error         node_modules/typescript-eslint
npm error     1 more (@typescript-eslint/typescript-estree)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.1.0" from typescript-eslint@8.67.0
npm error node_modules/typescript-eslint
npm error   dev typescript-eslint@"^8.67.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.4 <6.1.0" from typescript-eslint@8.67.0
npm error   node_modules/typescript-eslint
npm error     dev typescript-eslint@"^8.67.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-15T13_18_01_807Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-15T13_18_01_807Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/typescript-7.x branch from 7795bae to f8558ce Compare August 13, 2026 04:58
henry-nsheaps[bot]

This comment was marked as outdated.

henry-nsheaps[bot]

This comment was marked as outdated.

henry-nsheaps[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/typescript-7.x branch 2 times, most recently from d26e606 to 92624e6 Compare August 27, 2026 00:06
henry-nsheaps[bot]

This comment was marked as outdated.

@henry-nsheaps henry-nsheaps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Review — chore(deps): update dependency typescript to v7 (rebased to 2578f4c8)

Summary

Renovate rebased this PR onto latest main today (new head 2578f4c8, 2026-08-28T17:14:45Z) to pick up merged updates to jsdom (→ ^30.0.1, #42) and Node engines (→ >=24.18.1, #41), plus a workflow-file sync (a40460c.github/workflows/dispatch-review.yaml). The PR's own diff remains byte-identical to prior reviews: a single-line bump of typescript from ^6.0.3^7.0.2 in package.json. No coordinated typescript-eslint bump landed on main (still ^8.65.0), and Renovate's ERESOLVE artifact-update report was refreshed at 2026-08-28T17:14:52Z with the same failure signature.

Recommendation

🚫 Request changes / do not merge — same P0 as before, no fix. See the inline comment on package.json:54 for the full breakdown. typescript-eslint@8.65.0 still declares peer typescript: ">=4.8.4 <6.1.0", so npm install errors with ERESOLVE and package-lock.json cannot be regenerated. Merging as-is would leave main in a state where npm ci fails, breaking every CI job that installs deps (lint, typecheck, test, build, e2e).

Strengths

  • ✅ Scope is minimal (one line, one file) — trivial to review and revert.
  • ✅ Renovate proactively surfaced the ERESOLVE failure and re-refreshed it after today's rebase, rather than producing a silently-broken lockfile.
  • ✅ Follows the project's Renovate-driven dependency-update flow (renovate.json extends nsheaps/renovate-config).

Issues

🚨 P0 — Blocking peer-dependency conflict; broken install after merge (details in the inline comment on package.json:54)
  • typescript-eslint@8.65.0@typescript-eslint/{eslint-plugin,parser,type-utils,typescript-estree,utils,project-service,tsconfig-utils}@8.65.0 all declare peer typescript: ">=4.8.4 <6.1.0".
  • Bumping typescript to ^7.0.2 violates every one of those peer ranges — Renovate's refreshed artifact-update comment (2026-08-28T17:14:52Z) shows npm error code ERESOLVE ... Conflicting peer dependency: typescript@6.0.3.
  • Upstream is aware TS 7 is coming (typescript-eslint#12529 "add warning when TS 7 is detected" shipped in 8.65.0) but hasn't widened the peer range — the linter package explicitly refuses TS 7 and warns if you force-install.
  • Because no package-lock.json accompanies the package.json change, npm ci on main after merge will fail. Build-blocker, not just typecheck.

Full recommended remediations (grouped update / allowedVersions pin / coordinated bump) are in the inline comment on package.json:54. Do not use --legacy-peer-deps; do not soften strictness (CLAUDE.md bans any / @ts-ignore).

ℹ️ P2 — PR body / release notes are effectively empty

The Renovate-generated release-notes section links to a bare compare URL (v6.0.3...2bd066d87f5bafd315be9f40889d0a60b9e58e0b) with no changelog excerpt. TypeScript 7 is a major version bump and almost certainly contains breaking changes affecting a strict-mode codebase. Before this PR (or its grouped successor) can be safely merged, please add a short summary of the TS 7 breaking changes that actually touch this repo (strictness, module resolution, decorator behavior, lib defaults, etc.) so reviewers can assess impact rather than trusting ^7.0.2 blindly.

Non-blocking on its own, but pairs with the P0 — the fix for the P0 will need the same context.

What (didn't) change since last review

  • package.json:54 is byte-identical to the prior review head (92624e6); the rebase to 2578f4c8 only pulled in unrelated base-branch bumps (jsdom, Node engines, a workflow-file sync).
  • typescript-eslint is unchanged on main at ^8.65.0; peer range still >=4.8.4 <6.1.0. No new upstream release resolves this.
  • Renovate's ERESOLVE report was updated 2026-08-28T17:14:52Z with the same failure signature.
  • No response to prior reviews' suggestions; no engagement to reply to.

Follow-ups

  • 🟥 P0 — Resolve the peer-dep conflict (grouped update, allowedVersions ignore, or coordinated typescript-eslint bump). Until then this PR should not merge.
  • 🟨 P2 — Add a TS 7 breaking-changes callout to the PR body (or its grouped successor).

Verdict

REQUEST_CHANGES — same blocker as before, unchanged after today's rebase; one P0 (peer-dep conflict / broken install) + one P2 (missing release-notes context).


References:

Reviewed against commit 2578f4c8 on branch renovate/typescript-7.x. Findings based on the PR diff, the PR-branch package.json (typescript-eslint: ^8.65.0 on line 55), Renovate's refreshed ERESOLVE artifact report (comment 5261781302, 2026-08-28T17:14:52Z), the branch commit history (last change to the PR diff was Renovate's rebase on 2026-08-28T17:14:45Z; no code or lockfile added), renovate.json (extends local>nsheaps/renovate-config), and CLAUDE.md conventions. Previous reviews (against f8558ce, d534ccc, a7547ce, 92624e6) and their inline duplicates minimized as outdated; a fresh inline comment on package.json:54 accompanies this review. No CI output was used to form this assessment.

Comment thread package.json
"globals": "^17.8.0",
"jsdom": "^30.0.1",
"typescript": "^6.0.3",
"typescript": "^7.0.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🚨 P0 — Blocking peer-dep conflict; npm install still fails after 2026-08-28 rebase

Renovate rebased this PR again today (new head 2578f4c8, 2026-08-28T17:14:45Z) to pick up merged updates to jsdom (→ ^30.0.1, #42) and Node engines (→ >=24.18.1, #41), plus a workflow-file sync. No typescript-eslint bump landed on main (still ^8.65.0 on package.json:55), so nothing about the peer-dep situation has changed. Renovate's refreshed artifact-update comment (updated 2026-08-28T17:14:52Z) shows the same ERESOLVE failure:

npm error code ERESOLVE
npm error While resolving: typescript-eslint@8.65.0
npm error Found: typescript@7.0.2
...
npm error Conflicting peer dependency: typescript@6.0.3
npm error peer typescript@">=4.8.4 <6.1.0" from typescript-eslint@8.65.0

typescript-eslint@8.65.0 and every @typescript-eslint/*@8.65.0 subpackage still declare peer typescript: ">=4.8.4 <6.1.0". Bumping typescript to ^7.0.2 violates that range, so npm cannot regenerate package-lock.json. Upstream shipped typescript-eslint#12529 "add warning when TS 7 is detected" in 8.65.0 but has not widened the peer range — the linter package explicitly refuses TS 7.

Because no updated package-lock.json accompanies this package.json change, merging as-is will break npm ci on main for every CI job that installs deps (lint, typecheck, test, build, e2e). This is a build-blocker, not just a typecheck concern.

Recommended options (any one unblocks):

  1. Preferred — hold this PR until typescript-eslint publishes a release whose peer range includes TS 7, then bump both together. A Renovate packageRules grouping in the shared nsheaps/renovate-config (e.g. matchPackageNames: ["typescript", "typescript-eslint", "@typescript-eslint/**"], groupName: "typescript") would prevent this class of broken PR going forward.
  2. Close this PR and add a temporary allowedVersions: "<7" entry for typescript in Renovate config until the ecosystem catches up, to avoid re-opening the same broken PR on every rebase.
  3. Only if you accept the ecosystem-compat risk: extend this PR to also bump typescript-eslint to a version whose peer range covers TS 7, then re-run Renovate so the lockfile actually regenerates. Do not patch around this with --legacy-peer-deps — that hides the fact that the linter's TS API assumptions may not hold under a TS major bump.

Per CLAUDE.md ("TypeScript strict — no any, no @ts-ignore"), silently softening strictness to squeeze past a TS 7 breaking change is not an option either.

Findings based on the diff at package.json:54, package.json:55 on the PR branch (typescript-eslint: ^8.65.0), Renovate's refreshed ERESOLVE report (comment 5261781302, 2026-08-28T17:14:52Z), the typescript-eslint@8.65.0 CHANGELOG, and renovate.json (extends local>nsheaps/renovate-config). Previous inline comments on this line are byte-nearly-identical and are minimized as outdated.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant