Skip to content

chore(deps): update dependency typescript to v6 (main)#8413

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/main-major-typescript
Open

chore(deps): update dependency typescript to v6 (main)#8413
renovate[bot] wants to merge 1 commit intomainfrom
renovate/main-major-typescript

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 28, 2026

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^5.9.3^6.0.2 age confidence

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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.


  • 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 added the dependencies Pull requests that update a dependency file label Mar 28, 2026
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Mar 28, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 28, 2026

⚠️ 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 stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nextcloud/eslint-config@8.4.2
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"^6.0.2" from the root project
npm error   peerOptional typescript@">=4.7.4" from @vue/eslint-config-typescript@13.0.0
npm error   node_modules/@vue/eslint-config-typescript
npm error     peer @vue/eslint-config-typescript@"^13.0.0" from @nextcloud/eslint-config@8.4.2
npm error     node_modules/@nextcloud/eslint-config
npm error       dev @nextcloud/eslint-config@"^8.4.2" from the root project
npm error   7 more (@vue/language-core, ts-api-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.0.2" from @nextcloud/eslint-config@8.4.2
npm error node_modules/@nextcloud/eslint-config
npm error   dev @nextcloud/eslint-config@"^8.4.2" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@"^5.0.2" from @nextcloud/eslint-config@8.4.2
npm error   node_modules/@nextcloud/eslint-config
npm error     dev @nextcloud/eslint-config@"^8.4.2" 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-03-28T08_24_31_538Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-28T08_24_31_538Z-debug-0.log

@github-actions github-actions bot enabled auto-merge March 28, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants