Skip to content

[Snyk] Fix for 3 vulnerabilities - #760

Open
pushkala-datastax wants to merge 1 commit into
2.10_dsfrom
snyk-fix-9457a3f368e8e81c6e381807d52c1243
Open

[Snyk] Fix for 3 vulnerabilities#760
pushkala-datastax wants to merge 1 commit into
2.10_dsfrom
snyk-fix-9457a3f368e8e81c6e381807d52c1243

Conversation

@pushkala-datastax

Copy link
Copy Markdown
Collaborator

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • site2/website-next/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Uncontrolled Recursion
SNYK-JS-AXIOS-18060730
  738  
medium severity Prototype Pollution
SNYK-JS-AXIOS-18065349
  708  
medium severity Prototype Pollution
SNYK-JS-AXIOS-18065355
  708  

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:

🦉 Uncontrolled Recursion
🦉 Prototype Pollution

@pushkala-datastax

Copy link
Copy Markdown
Collaborator Author

Merge Risk: High

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

Key Breaking Changes:

  • MDX v1 → v3 Upgrade: This is the most significant breaking change. MDX v3 is much stricter about parsing content. Markdown files (.md, .mdx) that previously worked may now fail to compile or render differently, especially those containing unescaped < or { characters. [1, 2, 3] You should use the npx docusaurus-mdx-checker command to identify files that need modification. [1, 6]

  • React 17 → 18 Upgrade: Docusaurus now requires React 18. [1, 2, 3] This can introduce subtle breaking changes, such as new hydration errors and differences in state update batching, which may affect custom React components or swizzled theme components. [1, 3]

  • Node.js Version: Support for Node.js 16 has been dropped. The new minimum required version is Node.js 18.0+. [1, 3]

  • Docusaurus API & Theming:

    • The :::caution admonition is deprecated and should be replaced with :::warning. [2]
    • Internal theme components have been refactored. If you have customized components using the swizzle command, you may need to re-swizzle and adapt your customizations. [2]

Recommendation:
This upgrade cannot be performed without manual intervention. Developers must follow the official migration guide carefully. Start by running the docusaurus-mdx-checker tool to estimate the content migration effort and then address the dependency and API changes.

Source: Official Docusaurus v3 Upgrade Guide [1, 4]

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants