Skip to content

Update dependency typescript to v7#1977

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

Update dependency typescript to v7#1977
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/typescript-7.x

Conversation

@renovate

@renovate renovate Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^6.0.0^7.0.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source


Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, 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 commented Jul 8, 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: dev/xml-formatter/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @typescript-eslint/eslint-plugin@8.63.0
npm ERR! Found: typescript@7.0.2
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"^7.0.0" from the root project
npm ERR!   peer typescript@">=4.8.4" from ts-api-utils@2.5.0
npm ERR!   node_modules/ts-api-utils
npm ERR!     ts-api-utils@"^2.5.0" from @typescript-eslint/eslint-plugin@8.63.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm ERR!     ts-api-utils@"^2.5.0" from @typescript-eslint/type-utils@8.63.0
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"8.63.0" from @typescript-eslint/eslint-plugin@8.63.0
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (ts-node)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.63.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"^8.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@6.0.3
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.63.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^8.0.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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-13T03_34_02_346Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/typescript-7.x branch 4 times, most recently from 052a063 to 2b70f55 Compare July 12, 2026 03:03
@renovate renovate Bot force-pushed the renovate/typescript-7.x branch from 2b70f55 to aace4dc Compare July 13, 2026 03:34
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.

0 participants