[Snyk] Security upgrade gatsby from 2.32.13 to 5.14.0

[saurabharch]

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

Snyk changed the following file(s):

• examples/using-path-prefix/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12704893	788
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12761655	788
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-12613773	738

---

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, 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 is an automated security update initiated by Snyk to mitigate critical vulnerabilities within the project's dependencies. By upgrading the Gatsby framework to its latest stable version, the PR ensures the application benefits from the most recent security patches, thereby enhancing its overall resilience against known exploits without requiring manual intervention for the fix.

Highlights

• Security Vulnerability Fix: This pull request, automatically generated by Snyk, addresses three security vulnerabilities in the project's npm dependencies.
• Dependency Upgrade: The gatsby dependency has been upgraded from version 2.32.13 to 5.14.0 to resolve the identified security issues.
• Vulnerabilities Addressed: The fix targets two high-severity Server-side Request Forgery (SSRF) vulnerabilities (SNYK-JS-IP-12704893, SNYK-JS-IP-12761655) and one medium-severity Allocation of Resources Without Limits or Throttling vulnerability (SNYK-JS-AXIOS-12613773).

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

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, upgrades Gatsby from version 2 to 5 to address several security vulnerabilities. While this is an important security update, it's a major version upgrade that introduces breaking changes. The current change is incomplete and will break the using-path-prefix example. Specifically:

• Gatsby v5 requires React 18, but the react and react-dom dependencies have not been updated from version 16.
• Gatsby v5 also requires Node.js 18 or newer. You should ensure your build and deployment environment meets this requirement.

The React version incompatibility is a critical issue that will prevent the project from building. I have added a specific comment with a suggestion to fix it.

[gemini-code-assist]

Upgrading to Gatsby v5 is a major change that requires other dependencies to be updated as well. Gatsby v5 has a peer dependency on React 18, but the react and react-dom packages are still on version 16. This incompatibility will break the build. Please upgrade react and react-dom to a compatible version, for example ^18.2.0.

Suggested change

	"gatsby": "^5.14.0",
	"react": "^16.4.0",
	"react-dom": "^16.4.0"
	"gatsby": "^5.14.0",
	"react": "^18.2.0",
	"react-dom": "^18.2.0"