chore(deps): update dependency ts-loader to v9.6.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-loader	9.5.1 → 9.6.2

---

Release Notes

TypeStrong/ts-loader (ts-loader)

v9.6.2

Compare Source

• chore: trim runtime dependencies — remove enhanced-resolve/semver, swap micromatch → picomatch - thanks @​johnnyreilly

Officially ts-loader has supported 3.6.3+ versions of TypeScript. This change means that certain scenarios with older versions of TS will now certainly fail. If anyone is actually using these versions it would be surprising.

v9.6.1

Compare Source

• fix: rspack support - thanks @​johnnyreilly and @​bhollis

v9.6.0

Compare Source

• feat: add webpack 4 support back - thanks @​johnnyreilly and @​tweet

v9.5.7

Compare Source

• fix: TS5011 errors with TypeScript 6.0: transpileModule called with rootDir: undefined [#​1678] - thanks @​julioz and @​errorx666
• feat: migrate to trusted publishing - thanks @​johnnyreilly

Skipping 9.5.5-9.5.6 due to publishing issues

v9.5.4

Compare Source

• chore: typescript 5.9 upgrade - thanks @​johnnyreilly

Skipping 9.5.3 due to a publishing issue

v9.5.2

Compare Source

• fix: add more detailed error messages - thanks @​hai-x

---

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

[renovate]

⚠️ 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 cli npm v12.0.1 does not support Node.js v20.16.0. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm error code ERR_REQUIRE_ESM
npm error require() of ES Module /opt/containerbase/tools/npm/12.0.1/20.16.0/node_modules/npm/node_modules/@npmcli/agent/node_modules/http-proxy-agent/dist/index.js from /opt/containerbase/tools/npm/12.0.1/20.16.0/node_modules/npm/node_modules/@npmcli/agent/lib/proxy.js not supported.
npm error Instead change the require of index.js in /opt/containerbase/tools/npm/12.0.1/20.16.0/node_modules/npm/node_modules/@npmcli/agent/lib/proxy.js to a dynamic import() which is available in all CommonJS modules.
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-18T04_07_25_019Z-debug-0.log