Skip to content

[Snyk] Fix for 1 vulnerabilities#38

Open
GG-TechOpsSuper wants to merge 1 commit into
mainfrom
snyk-fix-0e9bc6e75e32e235ead6e20506423b25
Open

[Snyk] Fix for 1 vulnerabilities#38
GG-TechOpsSuper wants to merge 1 commit into
mainfrom
snyk-fix-0e9bc6e75e32e235ead6e20506423b25

Conversation

@GG-TechOpsSuper

Copy link
Copy Markdown

snyk-top-banner

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
critical severity Command Injection
SNYK-JS-REACTDEVUTILS-17890708
  740  

Breaking Change Risk

Merge Risk: High

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:

🦉 Command Injection

@GG-TechOpsSuper

Copy link
Copy Markdown
Author

Merge Risk: High

This is a major version upgrade from Docusaurus v2 to v3, which introduces significant and mandatory breaking changes. Action is required to ensure the site builds and functions correctly.

Key Breaking Changes:

  • MDX v3 Upgrade: The most impactful change is the upgrade from MDX v1 to MDX v3. [1, 5] MDX v3 has a much stricter parser, and content that worked with Docusaurus v2 may now fail to build. [3] Special characters like < and { are handled differently. Developers must review and potentially fix existing .md and .mdx files.
  • Node.js Requirement: Docusaurus v3 requires Node.js v18.0+. [1, 5] Support for Node.js v16 has been dropped.
  • React Requirement: Docusaurus v3 requires React v18.0+. [1, 5]
  • Other Dependency Upgrades: Key dependencies like prism-react-renderer (for code blocks) and remark-emoji have been upgraded to new major versions, which could introduce subtle changes. [1]

Recommendation:

  1. Update your CI and local development environments to Node.js v18+.
  2. Run the npx docusaurus-mdx-checker command on your project to identify content files that need to be fixed for MDX v3 compatibility. [1]
  3. Thoroughly review the official migration guide before upgrading.

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

GG-TechOpsSuper commented Jul 9, 2026

Copy link
Copy Markdown
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants