[Snyk] Fix for 2 vulnerabilities

[ioncakephper]

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• sample/sample-doc/package.json
• sample/sample-doc/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
	Origin Validation Error SNYK-JS-WEBPACKDEVSERVER-10300775	142
	Exposed Dangerous Method or Function SNYK-JS-WEBPACKDEVSERVER-10300777	129

---

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.

Description by Korbit AI

What change is being made?

Update Docusaurus dependencies in sample/sample-doc/package.json from 3.6.3 to 3.9.0 (core and preset-classic).

Why are these changes being made?

To fix vulnerabilities identified by Snyk; newer versions include security fixes with no expected behavioral changes.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[korbit-ai]

I've completed my review and didn't find any issues... but I did find this bear.

/  \.-"""-./  \
\    -   -    /
 |   o   o   |
 \  .-'''-.  /
  '-\__Y__/-'
     `---`

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

[gemini-code-assist]

Summary of Changes

Hello @ioncakephper, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the security posture of the project by resolving two identified vulnerabilities within the sample/sample-doc module. The fix involves upgrading the @docusaurus/core and @docusaurus/preset-classic dependencies to their latest stable version, 3.9.0, thereby mitigating a high-severity 'Origin Validation Error' and a medium-severity 'Exposed Dangerous Method or Function'.

Highlights

• Vulnerability Fixes: This pull request addresses two security vulnerabilities: a high-severity 'Origin Validation Error' (SNYK-JS-WEBPACKDEVSERVER-10300775) and a medium-severity 'Exposed Dangerous Method or Function' (SNYK-JS-WEBPACKDEVSERVER-10300777).
• Dependency Upgrades: To resolve the identified vulnerabilities, the @docusaurus/core and @docusaurus/preset-classic dependencies have been upgraded from version 3.6.3 to 3.9.0.
• Automated PR Creation: This pull request was automatically generated by Snyk to provide a direct fix for the detected security issues.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix two vulnerabilities by upgrading @docusaurus/core and @docusaurus/preset-classic. While the intention is good, this upgrade introduces critical breaking changes. The new Docusaurus version (3.9.0) requires React 18 and MDX v3, but the project's dependencies for react, react-dom, and @mdx-js/react have not been updated accordingly. This will likely lead to build failures. I've added a critical comment with details on how to resolve this.

[gemini-code-assist]

Upgrading @docusaurus/core and @docusaurus/preset-classic to version 3.9.0 is a major version update to Docusaurus v3. This version has breaking changes, including:

• A peer dependency on React 18 ("react": "^18.0.0"). The project is currently using React 16 ("react": "^16.8.4").
• An upgrade to MDX v3, which requires @mdx-js/react@^3.0.0. The project is currently using ^1.6.22.

These outdated dependencies will likely cause build failures. Please upgrade react, react-dom, and @mdx-js/react to their compatible versions. For a full migration, you should follow the Docusaurus v3 migration guide.

Here is an example of what your dependencies should look like:

"dependencies": {
  "@docusaurus/core": "3.9.0",
  "@docusaurus/preset-classic": "3.9.0",
  "@mdx-js/react": "^3.0.0",
  "clsx": "^2.0.0",
  "react": "^18.0.0",
  "react-dom": "^18.0.0"
}