Update dependency typescript to ~5.7.0

[gisbdzhch]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	~5.5.4 -> ~5.7.0

---

Release Notes

microsoft/TypeScript (typescript)

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.7.0 (Beta).
• fixed issues query for Typescript 5.7.1 (RC).
• fixed issues query for Typescript 5.7.2 (Stable).
• fixed issues query for Typescript 5.7.3 (Stable).

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.7.0 (Beta).
• fixed issues query for Typescript 5.7.1 (RC).
• fixed issues query for Typescript 5.7.2 (Stable).

Downloads are available on:

• npm

v5.6.3: TypeScript 5.6.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.6.0 (Beta).
• fixed issues query for Typescript 5.6.1 (RC).
• fixed issues query for Typescript 5.6.2 (Stable).
• fixed issues query for Typescript 5.6.3 (Stable).

Downloads are available on:

• npm
• NuGet package

v5.6.2: TypeScript 5.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.6.0 (Beta).
• fixed issues query for Typescript 5.6.1 (RC).
• fixed issues query for Typescript 5.6.2 (Stable).

Downloads are available on:

• npm
• NuGet package

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Renovate Bot.

[Tugark]

@wendlans This cannot be updated, even with angular 19 (see #91 (comment)). We _could_fix the buildtime compiler warning for @uppy, but not for @arcgis.

As such, I think it's a bit dangerous to have these updates in renovate, because the build is seemingly working. We'll have to wait and see what happens when our pipelines are fixed next sprint.

[Tugark]

@wendlans This cannot be merged since it breaks with angular during install (Angular 19 requires <5.7); and it would break during runtime due to arcgis.

I think we could exclude typescript from renovate config, since it's highly likely that this will always have some issues (I mean, no packages will use bleeding edge versions, I guess). Thoughts?

Note: We could try and manually update to 5.6, but I'm not sure it is worth the hassle. Actually no, because that would break arcgis :)

[wendlans]

@wendlans This cannot be merged since it breaks with angular during install (Angular 19 requires <5.7); and it would break during runtime due to arcgis.

I think we could exclude typescript from renovate config, since it's highly likely that this will always have some issues (I mean, no packages will use bleeding edge versions, I guess). Thoughts?

Note: We could try and manually update to 5.6, but I'm not sure it is worth the hassle. Actually no, because that would break arcgis :)

@Tugark AFAIK we can block Typescript entirely from the Renovate config. The effect would be that Typescript wouldn't be mentioned even in case Angular gets updated.
Should we do that including patch level changes?

[Tugark]

@wendlans This cannot be merged since it breaks with angular during install (Angular 19 requires <5.7); and it would break during runtime due to arcgis.
I think we could exclude typescript from renovate config, since it's highly likely that this will always have some issues (I mean, no packages will use bleeding edge versions, I guess). Thoughts?
Note: We could try and manually update to 5.6, but I'm not sure it is worth the hassle. Actually no, because that would break arcgis :)

@Tugark AFAIK we can block Typescript entirely from the Renovate config. The effect would be that Typescript wouldn't be mentioned even in case Angular gets updated. Should we do that including patch level changes?

Yes, I'd prefer that. We will always have have some issues with it, and it needs manual checking anyhow (given that we cannot reliably trust renovate.

Or: Because I like this as a "reminder", we could also close this PR, then it should not be opened again for this version. It would be opened again, I think, for 5.7.1 - if that happens too frequently, then I would disable typescript in renovate altogether.

Thoughts @wendlans ?

[wendlans]

@Tugark AFAIK we can block Typescript entirely from the Renovate config. The effect would be that Typescript wouldn't be mentioned even in case Angular gets updated. Should we do that including patch level changes?

Yes, I'd prefer that. We will always have have some issues with it, and it needs manual checking anyhow (given that we cannot reliably trust renovate.

Or: Because I like this as a "reminder", we could also close this PR, then it should not be opened again for this version. It would be opened again, I think, for 5.7.1 - if that happens too frequently, then I would disable typescript in renovate altogether.

Thoughts @wendlans ?

I'm not sure how good a reminder is that we don't really use. On the other hand if it does not pop up every day we should be fine. I think we can go with the later for now. @Tugark I'll close this PR for now.

[Tugark]

@Tugark AFAIK we can block Typescript entirely from the Renovate config. The effect would be that Typescript wouldn't be mentioned even in case Angular gets updated. Should we do that including patch level changes?

Yes, I'd prefer that. We will always have have some issues with it, and it needs manual checking anyhow (given that we cannot reliably trust renovate.
Or: Because I like this as a "reminder", we could also close this PR, then it should not be opened again for this version. It would be opened again, I think, for 5.7.1 - if that happens too frequently, then I would disable typescript in renovate altogether.
Thoughts @wendlans ?

I'm not sure how good a reminder is that we don't really use. On the other hand if it does not pop up every day we should be fine. I think we can go with the later for now. @Tugark I'll close this PR for now.

A reminder in the sense that we know that typescript has a new version and we can (or should) then manually check if it is now working.

Basically, just like I did with this update here :D

[gisbdzhch]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (~5.7.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.