breaking: the dependency typescript has been updated to a new major version (6.0.3), which may include breaking changes. #major

[public-glueops-renovatebot]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 6.0.3

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3: TypeScript 6.0.3

Compare Source

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

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

v6.0.2: TypeScript 6.0

Compare Source

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

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[public-glueops-renovatebot]

⚠️ 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: @sveltejs/kit@2.50.1
npm error Found: typescript@6.0.3
npm error node_modules/typescript
npm error   dev typescript@"6.0.3" from the root project
npm error   peer typescript@">=5.0.0" from svelte-check@4.3.5
npm error   node_modules/svelte-check
npm error     dev svelte-check@"4.3.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.3.3" from @sveltejs/kit@2.50.1
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"2.50.1" from the root project
npm error   peer @sveltejs/kit@"^2.0.0" from @sveltejs/adapter-auto@7.0.0
npm error   node_modules/@sveltejs/adapter-auto
npm error     dev @sveltejs/adapter-auto@"7.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.3.3" from @sveltejs/kit@2.50.1
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"2.50.1" from the root project
npm error     peer @sveltejs/kit@"^2.0.0" from @sveltejs/adapter-auto@7.0.0
npm error     node_modules/@sveltejs/adapter-auto
npm error       dev @sveltejs/adapter-auto@"7.0.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 /tmp/renovate/cache/others/npm/_logs/2026-05-17T00_07_19_425Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-05-17T00_07_19_425Z-debug-0.log

[public-glueops-renovatebot]

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.