[Snyk] Security upgrade @docusaurus/preset-classic from 3.8.1 to 3.9.0

[ahochsteger]

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

Snyk changed the following file(s):

• docs/package.json
• docs/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Origin Validation Error SNYK-JS-WEBPACKDEVSERVER-10300775	676
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Exposed Dangerous Method or Function SNYK-JS-WEBPACKDEVSERVER-10300777	621

---

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.

[gemini-code-assist]

Summary of Changes

Hello @ahochsteger, 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 upgrading the @docusaurus/preset-classic dependency. This update is critical as it resolves three identified vulnerabilities, including a high-severity issue related to origin validation in webpack-dev-server and two medium-severity vulnerabilities in inflight and webpack-dev-server, ensuring a more secure and stable application environment.

Highlights

• Security Upgrade: The primary purpose of this pull request is to upgrade the @docusaurus/preset-classic dependency from version 3.8.1 to 3.9.0.
• Vulnerability Fixes: This upgrade addresses three identified vulnerabilities, including a high-severity 'Origin Validation Error' (SNYK-JS-WEBPACKDEVSERVER-10300775) and two medium-severity issues ('Missing Release of Resource after Effective Lifetime' SNYK-JS-INFLIGHT-6095116 and 'Exposed Dangerous Method or Function' SNYK-JS-WEBPACKDEVSERVER-10300777).
• Automated Generation: This pull request was automatically created by Snyk to propose the necessary security fixes.

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 from Snyk aims to upgrade @docusaurus/preset-classic to version 3.9.0 to address several security vulnerabilities. While the intention is good, I've identified two significant issues. First, the PR fails to update other @docusaurus/* packages, leading to version inconsistencies that can cause problems in Docusaurus sites. All @docusaurus packages should be on the same version. Second, and more critically, the PR claims to fix the inflight vulnerability (SNYK-JS-INFLIGHT-6095116), but the resulting package-lock.json still includes a vulnerable version of inflight. This means the primary goal of fixing this vulnerability is not met. I've added specific comments with more details.

[gemini-code-assist]

The PR description states that it fixes the inflight vulnerability (SNYK-JS-INFLIGHT-6095116). However, the package-lock.json in this branch still contains inflight@1.0.6, which is a vulnerable version (the fix is in 1.0.7). This means the vulnerability is not actually remediated by this PR. Please investigate why the dependency was not updated correctly. It might be necessary to update other packages that have inflight as a transitive dependency, or use npm resolutions to force a newer version.

[gemini-code-assist]

While updating @docusaurus/preset-classic is correct, it's a strong recommendation for Docusaurus projects to keep all @docusaurus/* packages at the same version to avoid potential conflicts and subtle bugs. This PR leaves other packages like @docusaurus/core at 3.8.1. Please update all @docusaurus/* packages in dependencies and devDependencies to 3.9.0 for consistency. This will also prevent having two different versions of @docusaurus/core in your lockfile.