fix(deps): update dependency @microsoft/tsdoc-config to ^0.18.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@microsoft/tsdoc-config (source)	^0.16.0 → ^0.18.0

---

Release Notes

microsoft/tsdoc (@​microsoft/tsdoc-config)

v0.18.1

Compare Source

Wed, 25 Feb 2026 02:06:43 GMT

Patches

• Update the ajv dependency to ~8.18.0 to address CVE-2025-69873.

v0.18.0

Compare Source

Tue, 11 Nov 2025 00:51:42 GMT

Minor changes

• Normalize builtin imports.

Patches

• Remove test files and declaration maps from the published package.

v0.17.1

Compare Source

Sat, 23 Nov 2024 00:23:35 GMT

Patches

• Include CHANGELOG.md in published releases again

v0.17.0

Tue, 28 May 2024 21:34:19 GMT

Minor changes

• Minor package cleanup.

Patches

• Upgrade dev toolchain (Heft, Webpack, TypeScript)

v0.16.2

Wed, 14 Sep 2022 02:55:06 GMT

Version update only

v0.16.1

Sat, 09 Apr 2022 02:28:41 GMT

Patches

• Rename the "master" branch to "main."

---

Configuration

📅 Schedule: (UTC)

• 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.

[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: pnpm-lock.yaml

(node:1313) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)