[Snyk] Upgrade typedoc-plugin-markdown from 3.17.1 to 4.6.1

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade typedoc-plugin-markdown from 3.17.1 to 4.6.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 91 versions ahead of your current version.

• The recommended version was released 25 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	169	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	169	Proof of Concept

Release notes

Package name: typedoc-plugin-markdown

• 4.6.1 - 2025-04-02
  

  Patch Changes

  • Correctly render html table when interfacePropertiesFormat=htmlTable (#794).
  • Correctly handle overloaded function display in list and table views (#793).
  • Expose comments and signatures to index signature members.
  • Wrap default values in back ticks on table views to be consistent with list views.
  • Append semi colons to signature in code blocks.
• 4.6.0 - 2025-03-23
  

  Minor Changes

  • Implemented support for consuming TypeDoc core routers.
  • Exported routers to public api.
  • Implemented a hierarchy summary page as per default theme.
  • Updated "Constructor" titles of classes to fix internal anchor issues.

  Patch Changes

  • Fix incompatibility when used with "outputs" (#788).
  • Utilize "anchorPrefix" option to ensure unique anchors linking if required (#764).
• 4.5.2 - 2025-03-19
  

  Patch Changes

  • Ensure all file paths use forward slashes in windows (#782).
• 4.5.1 - 2025-03-18
  

  Patch Changes

  • Correctly handle package index paths (#782).
  • Make all options optional in PluginOptions interface (#781).
• 4.5.0 - 2025-03-16
• 4.4.2 - 2025-02-09
• 4.4.1 - 2025-01-01
• 4.4.0 - 2024-12-30
• 4.3.3 - 2024-12-18
• 4.3.2 - 2024-12-08
• 4.3.1 - 2024-12-01
• 4.3.0 - 2024-11-27
• 4.2.10 - 2024-11-01
• 4.2.9 - 2024-10-01
• 4.2.8 - 2024-09-22
• 4.2.7 - 2024-09-05
• 4.2.6 - 2024-08-25
• 4.2.5 - 2024-08-15
• 4.2.4 - 2024-08-13
• 4.2.3 - 2024-07-24
• 4.2.2 - 2024-07-22
• 4.2.1 - 2024-07-11
• 4.2.0 - 2024-07-10
• 4.1.2 - 2024-07-05
• 4.1.1 - 2024-06-30
• 4.1.0 - 2024-06-22
• 4.0.3 - 2024-05-27
• 4.0.2 - 2024-05-15
• 4.0.1 - 2024-05-06
• 4.0.0 - 2024-05-03
• 4.0.0-next.60 - 2024-04-29
• 4.0.0-next.59 - 2024-04-28
• 4.0.0-next.58 - 2024-04-21
• 4.0.0-next.57 - 2024-04-20
• 4.0.0-next.56 - 2024-04-19
• 4.0.0-next.55 - 2024-04-05
• 4.0.0-next.54 - 2024-03-21
• 4.0.0-next.53 - 2024-02-08
• 4.0.0-next.52 - 2024-02-07
• 4.0.0-next.51 - 2024-02-07
• 4.0.0-next.50 - 2024-02-02
• 4.0.0-next.49 - 2024-02-01
• 4.0.0-next.48 - 2024-02-01
• 4.0.0-next.47 - 2024-01-31
• 4.0.0-next.46 - 2024-01-30
• 4.0.0-next.45 - 2024-01-30
• 4.0.0-next.44 - 2024-01-30
• 4.0.0-next.43 - 2024-01-18
• 4.0.0-next.42 - 2024-01-18
• 4.0.0-next.41 - 2024-01-18
• 4.0.0-next.40 - 2024-01-12
• 4.0.0-next.39 - 2024-01-05
• 4.0.0-next.38 - 2023-12-18
• 4.0.0-next.37 - 2023-12-15
• 4.0.0-next.36 - 2023-12-03
• 4.0.0-next.35 - 2023-12-01
• 4.0.0-next.34 - 2023-11-30
• 4.0.0-next.33 - 2023-11-30
• 4.0.0-next.32 - 2023-11-29
• 4.0.0-next.31 - 2023-11-24
• 4.0.0-next.30 - 2023-11-20
• 4.0.0-next.29 - 2023-11-19
• 4.0.0-next.28 - 2023-11-18
• 4.0.0-next.27 - 2023-11-07
• 4.0.0-next.26 - 2023-11-07
• 4.0.0-next.25 - 2023-10-28
• 4.0.0-next.24 - 2023-10-20
• 4.0.0-next.23 - 2023-10-09
• 4.0.0-next.22 - 2023-09-26
• 4.0.0-next.21 - 2023-09-25
• 4.0.0-next.20 - 2023-08-29
• 4.0.0-next.19 - 2023-08-27
• 4.0.0-next.18 - 2023-08-10
• 4.0.0-next.17 - 2023-07-07
• 4.0.0-next.16 - 2023-06-13
• 4.0.0-next.15 - 2023-06-13
• 4.0.0-next.14 - 2023-06-12
• 4.0.0-next.13 - 2023-05-26
• 4.0.0-next.12 - 2023-05-17
• 4.0.0-next.11 - 2023-05-13
• 4.0.0-next.10 - 2023-04-26
• 4.0.0-next.9 - 2023-04-25
• 4.0.0-next.8 - 2023-04-21
• 4.0.0-next.7 - 2023-04-18
• 4.0.0-next.6 - 2023-04-16
• 4.0.0-next.5 - 2023-04-14
• 4.0.0-next.4 - 2023-04-11
• 4.0.0-next.3 - 2023-02-04
• 4.0.0-next.2 - 2023-01-30
• 4.0.0-next.1 - 2023-01-29
• 4.0.0-next.0 - 2023-01-22
• 3.17.1 - 2023-11-06

from typedoc-plugin-markdown GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Build:

• Update the typedoc-plugin-markdown version in the artifact package's dependencies.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request is an automated dependency upgrade by Snyk to update the typedoc-plugin-markdown package from version 3.17.1 to 4.6.1. This is a major version upgrade and may contain breaking changes. The upgrade aims to fix known security vulnerabilities.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgrade typedoc-plugin-markdown dependency	Updated the version of typedoc-plugin-markdown from 3.17.1 to 4.6.1	packages/artifact/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.