[Snyk] Fix for 3 vulnerabilities

[GG-TechOpsSuper]

Snyk has created this PR to fix 3 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
	Exposed Dangerous Method or Function SNYK-JS-WEBPACKDEVSERVER-10300777	770
	Exposed Dangerous Method or Function SNYK-JS-WEBPACKDEVSERVER-16642067	770
	Cross-site Request Forgery (CSRF) SNYK-JS-WEBPACKDEVSERVER-17812733	770

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:

🦉 Cross-site Request Forgery (CSRF)

[GG-TechOpsSuper]

The upgrade from Docusaurus v2.4.3 to v3.9.0 is a major version update with significant breaking changes that require developer action. The most impactful changes are the migration from MDX v1 to v3, the upgrade to React 18, and the requirement for Node.js 18+.

Key Breaking Changes:

• MDX v3 Upgrade: This is the most significant change. MDX v3 is much stricter about syntax. Markdown files (.md/.mdx) that compiled successfully in v2 may now fail to build. You will need to audit your content for issues, particularly the use of < and { characters.

  • Action: Use the npx docusaurus-mdx-checker command to identify files that need modification.

• Node.js Requirement: Docusaurus v3 requires Node.js 18.0 or newer. Support for Node.js 16 has been dropped.

  • Action: Ensure your local development and CI/CD environments are updated to Node.js 18+.

• React 18 Upgrade: The upgrade to React 18 may affect custom React components. Be aware of changes like automatic batching and new hydration errors.

  • Action: Test any custom React components and review the official React 18 upgrade guide.

• Other Notable Changes:

  • The :::caution admonition is deprecated and should be replaced with :::warning.
  • The official TypeScript configuration has moved from @tsconfig/docusaurus to @docusaurus/tsconfig.
  • If you have customized theme components using "swizzling", you may need to update them due to theme refactoring.

Recommendation:
This is a high-effort upgrade that cannot be completed by simply updating dependencies. Allocate time to thoroughly test your site, audit all MDX content, and update your build environment. Follow the official migration guide closely.

Source: Docusaurus v3 Upgrade Guide

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.