Skip to content

[Snyk] Fix for 1 vulnerabilities#60

Open
snyk-io[bot] wants to merge 1 commit intosailthrufrom
snyk-fix-1db71c7258abf7ceccab1487e0601910
Open

[Snyk] Fix for 1 vulnerabilities#60
snyk-io[bot] wants to merge 1 commit intosailthrufrom
snyk-fix-1db71c7258abf7ceccab1487e0601910

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Apr 14, 2026

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):

  • docusaurus/website/package.json
  • docusaurus/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
medium severity Improper Removal of Sensitive Information Before Storage or Transfer
SNYK-JS-FOLLOWREDIRECTS-16032162
  50  

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.

…o reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-FOLLOWREDIRECTS-16032162
@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Apr 14, 2026

Merge Risk: High

This is a major upgrade from an early alpha version to a stable release of Docusaurus 2. This version jump spans 75 alphas and 22 betas, and includes a complete stabilization of the Docusaurus v2 API. [9] Code written for 2.0.0-alpha.64 is not expected to be compatible with the stable 2.0.1 release.

Key Breaking Changes:

  • API Finalization: The entire API surface for @docusaurus/core and @docusaurus/preset-classic was finalized during the beta phase, introducing numerous breaking changes compared to the alpha versions. [1, 3, 5]
  • Build System: The build system was upgraded to Webpack 5 and PostCSS 8 during the alpha phase (alpha.75), which can affect custom plugins and styling. [19]
  • Configuration: Many configuration options in docusaurus.config.js were changed, added, or removed between the alpha and stable releases. [16, 17]
  • Theming: Theming and component swizzling have been significantly refactored. [1]

Recommendation:
This upgrade should be treated as a migration, not a simple dependency bump. Developers must follow the official Docusaurus v2 documentation and migration guides to update their site. Expect to refactor configuration, custom components, and styling to align with the stable v2 API.

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

@snyk-io snyk-io Bot requested review from Copilot and removed request for Copilot April 14, 2026 17:42
@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Apr 14, 2026

Snyk checks have failed. 5 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (5)
Open Source Security 1 4 0 0 5 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants