[Snyk] Security upgrade gatsby from 2.32.13 to 5.15.0

[saurabharch]

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

Snyk changed the following file(s):

• packages/homepage/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	529

---

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:

🦉 Cross-site Scripting (XSS)

[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 automates a critical security update by upgrading the "gatsby" framework to its latest stable version. The primary goal is to remediate a known Cross-site Scripting vulnerability, ensuring the application remains secure and robust against potential exploits.

Highlights

• Dependency Upgrade: The "gatsby" dependency in "packages/homepage/package.json" has been upgraded from version "2.13.45" to "5.15.0".
• Security Fix: This upgrade addresses a Cross-site Scripting (XSS) vulnerability (SNYK-JS-COOKIE-8163060) with a score of 529.

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. 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.32.13 to 5.15.0 to fix a security vulnerability. While addressing the security issue is important, this is a major version upgrade that introduces significant breaking changes. The current versions of other Gatsby-related packages, such as gatsby-cli and gatsby-image, are incompatible with Gatsby v5. Merging this change as-is will likely break the build and the site. I've added a critical comment with details on the required additional changes, including updating other dependencies and migrating from the deprecated gatsby-image to gatsby-plugin-image.

[gemini-code-assist]

This upgrade from Gatsby v2 to v5 is a major breaking change that will likely cause the application to fail. While it fixes the security vulnerability, several other dependencies are incompatible with Gatsby v5 and also need to be updated.

Specifically, from the surrounding lines:

• gatsby-cli at version ^2.7.21 is incompatible with Gatsby v5. It should be upgraded to a compatible version (e.g., ^5.15.0).
• gatsby-image (^2.2.30) is deprecated and has been replaced by gatsby-plugin-image in Gatsby v4. Migrating from gatsby-image to gatsby-plugin-image is required and involves code changes beyond just this package.json file.

You will need to follow the official Gatsby migration guides to handle the breaking changes:

• Migrating from v2 to v3
• Migrating from v3 to v4
• Migrating from v4 to v5

It's recommended to perform these major version upgrades incrementally (v2 -> v3 -> v4 -> v5) and update all gatsby-* plugins and themes accordingly to ensure a smoother transition.