[Snyk] Security upgrade gatsby from 1.0.0-beta.5-alpha.fb30fcd6 to 2.0.0

[saurabharch]

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

Snyk changed the following file(s):

• package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	828

---

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

[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 by upgrading the gatsby dependency to version 2.0.0. This upgrade specifically targets and resolves a high-severity vulnerability related to resource allocation, improving the overall robustness of the application.

Highlights

• Security Vulnerability Fix: This pull request addresses a high-severity security vulnerability (SNYK-JS-QS-14724253: Allocation of Resources Without Limits or Throttling) by upgrading the gatsby package.
• Dependency Upgrade: The gatsby dependency has been upgraded from version 1.0.0-beta.5-alpha.fb30fcd6 to 2.0.0.
• Automated PR: This pull request was automatically generated by Snyk to apply the security fix.
• Manual Intervention Required: The yarn.lock file was not updated by Snyk and requires manual updating before merging to ensure consistency, especially for zero-install users.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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, automatically generated by Snyk, upgrades Gatsby from a v1 beta version to v2.0.0 to resolve a security vulnerability. While addressing the security issue is important, this is a major version upgrade that introduces significant breaking changes. The application will not work without a considerable migration effort. Furthermore, the yarn.lock file has not been updated, which is a critical step that must be performed manually. My review comment provides details on the necessary migration steps, including updating other dependencies like React and Gatsby plugins, and refactoring code that uses deprecated or removed Gatsby APIs.

[gemini-code-assist]

Upgrading Gatsby from v1 to v2 is a major change with significant breaking changes that will break your application if not handled correctly. Merging this as-is will lead to a broken state.

Here are some of the required changes you'll need to make:

1. Update yarn.lock: The PR description notes that yarn.lock was not updated. You must run yarn to update it and commit the changes.
2. Update React: Gatsby v2 requires React v16. Your project is currently on React v15. You'll need to update react and react-dom.
3. Update Gatsby Plugins: All gatsby-* plugins must be updated to versions compatible with Gatsby v2. For example, gatsby-plugin-google-analytics, gatsby-plugin-react-helmet, etc., are on v1 versions.
4. API Migrations: Gatsby v2 introduced many API changes. You will need to update your code in:
   • gatsby-node.js: boundActionCreators is deprecated; use actions instead.
   • gatsby-browser.js: replaceComponentRenderer has been removed. You should use wrapRootElement or wrapPageElement.
   • gatsby-ssr.js: replaceRenderer has been removed. You should use wrapRootElement or wrapPageElement and replaceBodyHTMLString is used differently.
   • gatsby-link: The custom gatsby-link dependency is likely incompatible. Gatsby v2 has a built-in <Link> component which should be used instead.

I strongly recommend following the official Gatsby v1 to v2 migration guide to handle these changes properly.

[netlify]

❌ Error Happens

Name	Link
🔨 Latest commit	bcfe215
🔍 Latest deploy log	https://app.netlify.com/projects/wekanhow/deploys/69546938b056f20008c3b3c2