Skip to content

chore(deps): update typescript to 6.0.2#207

Open
zon-renovate wants to merge 1 commit intomainfrom
renovate/typescript-6.x
Open

chore(deps): update typescript to 6.0.2#207
zon-renovate wants to merge 1 commit intomainfrom
renovate/typescript-6.x

Conversation

@zon-renovate
Copy link
Copy Markdown
Collaborator

This PR contains the following updates:

Package Type Update Change
typescript (source) devDependencies major ^5.9.3^6.0.0

Release Notes

microsoft/TypeScript (typescript)

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

Downloads are available on:


Configuration

📅 Schedule: Branch creation - "before 5am on friday" 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 has been generated by Renovate Bot.

@zon-renovate
Copy link
Copy Markdown
Collaborator 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: app/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: @sveltejs/[email protected]
npm error Found: [email protected]
npm error node_modules/typescript
npm error   dev typescript@"^6.0.0" from the root project
npm error   peer typescript@">=5.0.0" from [email protected]
npm error   node_modules/svelte-check
npm error     dev svelte-check@"^4.3.6" from the root project
npm error   2 more (ts-api-utils, valibot)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.3.3" from @sveltejs/[email protected]
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"^2.50.2" from the root project
npm error   peer @sveltejs/kit@"^2.4.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/adapter-node
npm error     dev @sveltejs/adapter-node@"^5.5.2" from the root project
npm error   1 more (sveltekit-superforms)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.3.3" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"^2.50.2" from the root project
npm error     peer @sveltejs/kit@"^2.4.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-node
npm error       dev @sveltejs/adapter-node@"^5.5.2" from the root project
npm error     1 more (sveltekit-superforms)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-03-26T23_20_21_841Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-03-26T23_20_21_841Z-debug-0.log

@github-actions github-actions bot added the team-zoe Team Zoe label Mar 26, 2026
@witsch witsch added the blocked label Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants