Skip to content

[Snyk] Fix for 1 vulnerabilities - #47

Open
GG-TechOpsSuper wants to merge 1 commit into
mainfrom
snyk-fix-5f5279743c3c7219ddbb46b95f543581
Open

GG-TechOpsSuper wants to merge 1 commit into
mainfrom
snyk-fix-5f5279743c3c7219ddbb46b95f543581

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
high severity Inefficient Algorithmic Complexity
SNYK-JS-POSTCSSSELECTORPARSER-20510276
  610  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@GG-TechOpsSuper

Copy link
Copy Markdown
Author

Merge Risk: High

This major version upgrade from Docusaurus v2 to v3 introduces significant breaking changes requiring developer action. The most impactful change is the upgrade of the underlying content compiler from MDX v1 to MDX v3, which enforces stricter parsing of Markdown and may cause build failures.

Key Breaking Changes:

  • Environment Updates: Support for Node.js versions below 18.0 has been dropped. React has been upgraded to v18, which may affect custom React components.
  • MDX v3 Upgrade: This is the primary breaking change. Content files (.md, .mdx) will be compiled more strictly. Special characters like { and < may need to be escaped to prevent build errors. It is highly recommended to run npx docusaurus-mdx-checker to identify files that need modification.
  • 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.
  • Docusaurus API & Theming:
    • The :::caution admonition is deprecated and should be replaced with :::warning.
    • Users who have customized theme components via "swizzling" will likely need to re-apply their customizations to the new component structure.

Recommendation:
This is a high-impact upgrade that requires careful planning. Developers must review the official migration guide, test their content against the new MDX compiler, and verify any custom components. Allocate time for testing and content remediation before merging.

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 Oct 5, 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