[Snyk] Fix for 1 vulnerabilities

[saurabharch]

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

Snyk changed the following file(s):

• www/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863

---

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 @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 aims to enhance the project's security posture by upgrading key dependencies to address a critical vulnerability. The changes involve updating the gatsby framework and a related transformer plugin to their latest major versions, as recommended by Snyk for vulnerability remediation.

Highlights

• Security Vulnerability Fix: This pull request was automatically generated by Snyk to address a critical vulnerability (SNYK-JS-FORMDATA-10841150) identified as 'Predictable Value Range from Previous Values' in the project's npm dependencies.
• Dependency Upgrades: To remediate the vulnerability, the gatsby dependency has been upgraded from version ^2.0.53 to ^4.22.0, and gatsby-transformer-documentationjs has been upgraded from ^2.0.0 to ^3.0.0. These are significant major version bumps.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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 upgrades gatsby and gatsby-transformer-documentationjs to address a security vulnerability. The changes involve major version upgrades, which may introduce breaking changes. A manual migration is recommended to ensure compatibility and prevent site breakage.

[gemini-code-assist]

The upgrade of gatsby from v2 to v4 is a major version jump. This automated upgrade is likely to introduce breaking changes that require manual intervention to resolve. Consider a more cautious, manual migration, potentially upgrading incrementally (v2 -> v3, then v3 -> v4).

[gemini-code-assist]

Similar to the gatsby package update, this is a major version bump for gatsby-transformer-documentationjs. This upgrade may introduce breaking changes. Ensure compatibility with the updated gatsby version.