chore(deps): update dependency typescript to v5.7.2 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	5.4.3 -> 5.7.2

---

Release Notes

microsoft/TypeScript (typescript)

v5.7.2

Compare Source

v5.6.3

Compare Source

v5.6.2

Compare Source

v5.5.4: TypeScript 5.5.4

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 v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

v5.5.3: TypeScript 5.5.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 v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

v5.5.2: TypeScript 5.5

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 v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm

v5.4.5: TypeScript 5.4.5

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.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).
• fixed issues query for Typescript 5.4.5 (Stable).

Downloads are available on:

• NuGet package

v5.4.4: TypeScript 5.4.4

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.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).

Downloads are available on:

• 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 was generated by Mend Renovate. View the repository job log.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	22.7 MB	typescript-bot

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
License Policy Violation	npm/[email protected]	License: CC-BY-4.0 - Not allowed by license policy (package/ThirdPartyNoticeText.txt) License: W3C-20150513 - Not allowed by license policy (package/ThirdPartyNoticeText.txt)	package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]