Skip to content

[Snyk] Security upgrade @docusaurus/core from 3.9.0 to 3.10.2 - #61

Closed
HeyItsGilbert wants to merge 1 commit into
mainfrom
snyk-fix-429878299cbbcca2e1afddb18c3a6acf
Closed

[Snyk] Security upgrade @docusaurus/core from 3.9.0 to 3.10.2#61
HeyItsGilbert wants to merge 1 commit into
mainfrom
snyk-fix-429878299cbbcca2e1afddb18c3a6acf

Conversation

@HeyItsGilbert

Copy link
Copy Markdown
Member

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-18313070

Breaking Change Risk

Merge Risk: Medium

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.

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-JSYAML-18313070
@HeyItsGilbert

Copy link
Copy Markdown
Member Author

Merge Risk: Medium

This minor version upgrade of Docusaurus from 3.9.0 to 3.10.2 includes new features and bug fixes, with a low likelihood of breaking standard implementations. However, it introduces a significant internal refactoring that warrants a medium risk assessment.

Key Changes:

  • <Tabs> Component Refactor: The <Tabs> component was refactored to use React Context instead of props. While this is intended to improve extensibility, projects that have customized or swizzled the <Tabs> component may experience issues and require verification.
  • v4 Future Flags: The release introduces future.v4 flags, allowing users to opt-in to upcoming breaking changes for Docusaurus v4. These flags are disabled by default, but if you have globally enabled them, this upgrade may introduce breaking changes to your site.
  • Other Enhancements: The release also includes splitting the <DocCard> component for easier extension, compatibility with Algolia DocSearch 4.x, and various bug fixes across versions 3.10.1 and 3.10.2.

Recommendation:
It is recommended to verify the functionality of any customized <Tabs> components after the upgrade. If you are not using the future.v4 flags and have not swizzled the Tabs component, the upgrade is expected to be smooth.

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

Copilot AI review requested due to automatic review settings July 30, 2026 12:02
@netlify

netlify Bot commented Jul 30, 2026

Copy link
Copy Markdown

Deploy Preview for psake failed.

Name Link
🔨 Latest commit 54cdb75
🔍 Latest deploy log https://app.netlify.com/projects/psake/deploys/6a6b3d7324e3c30008616858

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This Snyk-generated pull request updates the Docusaurus core dependency to remediate a reported npm vulnerability in this Docusaurus-based documentation site.

Changes:

  • Bumps @docusaurus/core from 3.9.0 to 3.10.2 in package.json.

Comment thread package.json
Comment on lines +18 to 20
"@docusaurus/core": "3.10.2",
"@docusaurus/preset-classic": "3.9.0",
"@docusaurus/theme-mermaid": "3.9.0",
@HeyItsGilbert

Copy link
Copy Markdown
Member Author

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

  • SNYK-JS-JSYAML-18313070

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.


This action was performed automatically by Snyk.

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.

3 participants