SWI-3723 [Snyk] Fix for 2 vulnerabilities

[bwappsec]

Snyk has created this PR to fix 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	170
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	155

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:

🦉 Regular Expression Denial of Service (ReDoS)

[bwappsec]

This is a major version upgrade from Docusaurus v2 to v3 which introduces significant breaking changes. Action is required to ensure your site continues to build and function correctly.

Key Breaking Changes:

• Environment Updates:

  • Node.js: Support for Node.js v16 is dropped. You must use Node.js v18.0+.
  • React: Docusaurus now requires React v18.0+. This may introduce new hydration errors or behavioral changes like automatic batching that could affect custom components.

• MDX v3 Upgrade (High Impact):

  • The upgrade from MDX v1 to v3 is the most significant change and may cause build failures.
  • MDX v3 has stricter content parsing. Markdown files that previously compiled may now have errors or render differently.

• Configuration and Code Changes:

  • Syntax Highlighting: The import path for prism-react-renderer themes has changed. If you customized code block themes, you must update the import statements.
  • Admonitions: The :::caution admonition is deprecated and should be replaced with :::warning.
  • Swizzled Components: Internal theme components have been refactored. If you have customized components using the "swizzle" feature, you may need to update them.

Recommendation:

1. Update Environment: Ensure your development and deployment environments use Node.js v18+ and React v18+.
2. Check MDX Compatibility: Run npx docusaurus-mdx-checker on your project before upgrading to identify content files that will fail to compile under MDX v3.
3. Review the Official Guide: Follow the detailed steps in the official Docusaurus v3 Upgrade Guide.

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.

[bwappsec]

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

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

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