Skip to content

[Snyk] Fix for 1 vulnerabilities - #358

Open
rak-phillip wants to merge 1 commit into
masterfrom
snyk-fix-31f2818a3407298fca88b953c866e5bc
Open

[Snyk] Fix for 1 vulnerabilities#358
rak-phillip wants to merge 1 commit into
masterfrom
snyk-fix-31f2818a3407298fca88b953c866e5bc

Conversation

@rak-phillip

Copy link
Copy Markdown
Owner

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/package.json
  • docusaurus/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
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.

@rak-phillip

Copy link
Copy Markdown
Owner Author

Merge Risk: Medium

This upgrade of Docusaurus from version 3.8.1 to 3.10.2 introduces a required Node.js runtime change, which presents a medium risk.

Key Changes:

  • Node.js Requirement: Version 3.9.0 and later drop support for Node.js 18. The new minimum required version is Node.js 20. [5, 6] While the Docusaurus team considers this non-breaking as Node.js 18 is end-of-life, it is an environment change that may require action. [5]
  • v4 Future Flags: Version 3.10.0 introduces optional future.v4 flags to help users prepare for the upcoming Docusaurus v4. [4] These changes are opt-in and include stricter MDX handling and namespaced local storage. They will not impact builds unless explicitly enabled. [4]
  • New Features: The releases also include new features like support for Algolia DocSearch v4 and various bug fixes. [5, 2]

Recommendation:
Ensure your development and deployment environments are running Node.js version 20 or higher before upgrading.

Source: Docusaurus Release Notes

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

@github-actions

Copy link
Copy Markdown

🔄 Auto-Retry Failed Run

The Tests workflow run 30302945301 failed and has been automatically retried.

Follow up on the retried run here if needed: https://github.com/rak-phillip/dashboard/actions/runs/30302945301

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