SWI-3723 [Snyk] Fix for 1 vulnerabilities

[bwappsec]

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
	Prototype Pollution SNYK-JS-AXIOS-15252993	170

---

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:

🦉 Prototype Pollution

[bwappsec]

This major version upgrade from Docusaurus v2 to v3 introduces significant breaking changes, primarily centered around major dependency upgrades that require developer action.

Key Breaking Changes:

• MDX v1 → v3: This is the most impactful change. MDX v3 has stricter parsing, which may cause existing Markdown (.md and .mdx) files to fail during compilation. Special characters like < and { are now treated differently. A command-line tool is available to check for compatibility issues: npx docusaurus-mdx-checker.

• Node.js v16 → v18+: Support for Node.js v16 has been dropped. You must upgrade your development environment and any CI/CD pipelines to Node.js 18 or higher.

• React v17 → v18: The upgrade to React 18 introduces changes to the rendering APIs and other underlying behaviors.

• Other Breaking Changes:

  • The :::caution admonition is deprecated and should be replaced with :::warning.
  • The default number of entries in the blog RSS feed is now limited to 20.
  • Other dependencies like prism-react-renderer, react-live, and TypeScript have also been upgraded to new major versions.

Recommendation: This upgrade requires careful planning and testing. Before merging, developers must:

1. Ensure their environment uses Node.js v18+.
2. Run the npx docusaurus-mdx-checker tool to identify and fix content files that are incompatible with MDX v3.
3. Thoroughly test the site after upgrading dependencies to catch any issues arising from the React v18 upgrade.

Source: Docusaurus 3.0 Announcement, 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.