[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-jest/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, automatically generated by Snyk, focuses on enhancing the project's security posture by addressing critical vulnerabilities. It achieves this by performing a significant version upgrade of the gatsby dependency within the examples/using-jest project, thereby mitigating known Server-side Request Forgery (SSRF) and resource allocation issues.

Highlights

• Security Vulnerability Fix: This pull request addresses 3 identified security vulnerabilities (2 high, 1 medium severity) by upgrading the gatsby dependency.
• Dependency Upgrade: The gatsby package in examples/using-jest/package.json has been upgraded from version ^2.0.19 to ^5.14.0.
• Automated Security Remediation: This PR was automatically generated by Snyk to apply recommended 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

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 PR from Snyk upgrades gatsby from v2 to v5. This is a major version jump with significant breaking changes. The current change is incomplete and will break the application as it doesn't update other dependencies like React and Gatsby plugins, which are incompatible with Gatsby v5. A full migration is necessary.

[gemini-code-assist]

Upgrading gatsby from major version 2 to 5 will break the project. This is a significant update with many breaking changes that require a broader migration effort.

Here are some of the required changes:

• React Version: Gatsby v5 requires React 18. The react and react-dom dependencies must be upgraded from ^16.5.1 to ^18.0.0.
• Gatsby Plugins: All gatsby-* plugins are outdated and need to be upgraded to versions compatible with Gatsby v5. For example, gatsby-plugin-sharp is at ^2.0.7 and should be at ^5.13.1 or similar.
• gatsby-image: The gatsby-image package (^2.0.15) is deprecated and has been replaced by gatsby-plugin-image. This requires not only a dependency change but also code modifications where the Image component is used.
• StaticQuery component: The StaticQuery component is deprecated and should be replaced with the useStaticQuery hook. This will require refactoring the Layout component.
• Dev Dependencies: Development dependencies like react-test-renderer (^16.6.0) and babel-preset-gatsby (^0.1.2) are incompatible and must be updated.

Simply changing this one line will lead to build failures. I recommend addressing all these migration steps within this PR or creating a dedicated migration PR.