[Snyk] Fix for 1 vulnerabilities

[GG-TechOpsSuper]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• website/package.json
• website/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Arbitrary Code Injection SNYK-JS-GRAYMATTER-20532010	660

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Arbitrary Code Injection

[GG-TechOpsSuper]

The upgrade from Docusaurus v2.4.3 to v3.10.2 is a major version jump with significant and mandatory breaking changes that require developer action and environment updates.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js 16 is dropped. You must upgrade your development and deployment environments to Node.js v18.0 or newer.

• MDX v3 Upgrade: This is the most significant change. Docusaurus now uses MDX v3, which is much stricter than MDX v1.

  • Content that compiled successfully in v2 may now fail or render differently.
  • You will likely need to update .md and .mdx files to fix new parsing errors. A common fix is escaping bare { or < characters.
  • Action Required: Use the npx docusaurus-mdx-checker command to identify files that need modification before upgrading.

• React 18 Upgrade: Docusaurus now uses React 18, which introduces its own breaking changes, such as automatic batching and stricter hydration checks. Custom React components may be affected.

• Other Notable Changes:

  • The :::caution admonition is deprecated and should be replaced with :::warning.
  • The default limit for the blog RSS feed is now 20 entries.
  • Theme components have been refactored, which may require you to re-swizzle any customizations.

Source: Docusaurus v3 Upgrade Guide

Recommendation: This upgrade requires careful planning. Follow the official migration guide to prepare your site incrementally. Pay close attention to the MDX content changes, as they are the most likely source of issues.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[GG-TechOpsSuper]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.