build(deps-dev): bump typescript from 5.9.3 to 6.0.3 in /ui/mantine-ui

[dependabot]

Bumps typescript from 5.9.3 to 6.0.3.

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

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

TypeScript 6.0

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

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• 050880c Bump version to 6.0.3 and LKG
• eeae9dd 🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...
• ad1c695 🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)
• 0725fb4 🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...
• 607a22a Bump version to 6.0.2 and LKG
• 9e72ab7 🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...
• 35ff23d 🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...
• e175b69 Bump version to 6.0.1-rc and LKG
• af4caac Update LKG
• 8efd7e8 Merge remote-tracking branch 'origin/main' into release-6.0
• Additional commits viewable in compare view

[siavashs]

@dependabot rebase

[siavashs]

@sysadmind I think this is failing because of Node v24, I cannot reproduce the issue with Node v25.
Shall we upgrade the node version or skip the typescript upgrade?

[sysadmind]

currently, the odd versions of node never become LTS versions. That will change with v27 though. I would prefer to skip v25 and move to v26 as soon as it becomes "current" which should avoid issues where libraries aren't ready for the new version.

https://nodejs.org/en/about/previous-releases

Based on the CI output, there's some issue with the package-lock.json. When you run npm ci, the resolved dependencies must exactly match the lock file or it errors. When you run npm install, it will allow lock file corrections/edits. Do you think that's masking the issue for you locally? Did you try it on v24 locally? I think that the .nvmrc file should be managing the node version for the project.