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

[saurabharch]

Snyk has created this PR to fix 2 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
	Function Call With Incorrect Argument Type SNYK-JS-CIPHERBASE-12084814	848
	Function Call With Incorrect Argument Type SNYK-JS-SHAJS-12089400	848

---

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.

[netlify]

❌ Error Happens

Name	Link
🔨 Latest commit	1472036
🔍 Latest deploy log	https://app.netlify.com/projects/wekanhow/deploys/68ae48f911692b00081bae44

[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 upgrade initiated by Snyk to address two critical vulnerabilities by upgrading the gatsby dependency. The primary change involves updating the gatsby package version in package.json. Users leveraging Yarn's zero-install feature will need to manually run yarn to update their cache, as the yarn.lock file was not automatically updated.

Highlights

• Dependency Upgrade: Upgraded gatsby from version 1.0.0-beta.5-alpha.fb30fcd6 to 2.0.0.
• Security Fix: Addresses two critical vulnerabilities (SNYK-JS-CIPHERBASE-12084814 and SNYK-JS-SHAJS-12089400) related to "Function Call With Incorrect Argument Type".
• Manual Intervention Required: The yarn.lock file was not updated by Snyk, requiring a manual yarn command for zero-install users.

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 a v1 beta to v2.0.0 to resolve security vulnerabilities. While the upgrade is necessary, it's a major version bump with numerous breaking changes. The project will not build without a significant migration effort. My review highlights the critical issues that need to be addressed, such as upgrading React, updating all Gatsby plugins, and migrating to the new Gatsby v2 APIs. The official Gatsby migration guide should be followed closely to complete this upgrade.

[gemini-code-assist]

This upgrade to Gatsby v2 is a major version change with extensive breaking changes. Merging this PR as-is will break the application build.

This is a critical issue that requires a manual migration effort. Here are the main points to address:

• React Version: Gatsby v2 requires React v16. The project currently uses react: "15.5.4". You must upgrade react and react-dom to ^16.0.0 or higher.
• Gatsby Plugins: All gatsby-* plugins must be updated to their v2-compatible versions. For example, gatsby-plugin-google-analytics: "^1.0.1" and gatsby-plugin-react-helmet: "^1.0.1" are v1 plugins and will not work.
• gatsby-link: The gatsby-link component is now part of the main gatsby package in v2. The custom dependency "gatsby-link": "git+https://github.com/saurabharch/gatsby-link" should be removed, and all imports of Link should be changed from gatsby-link to gatsby.
• Gatsby APIs: The project's gatsby-*.js files use several v1 APIs that have been changed or removed in v2. These files need to be updated:
  • gatsby-node.js: boundActionCreators is replaced by actions. The onCreateWebpackConfig API and its configuration methods have changed.
  • gatsby-browser.js: replaceComponentRenderer is deprecated and should be replaced with wrapRootElement.
  • gatsby-ssr.js: replaceRenderer is deprecated and should be replaced with wrapRootElement or wrapPageElement.
• yarn.lock File: As the PR description warns, the yarn.lock file was not updated. After updating all the necessary dependencies in package.json, you must run yarn install to generate a new, consistent yarn.lock file.

It is highly recommended to follow the official Gatsby v1 to v2 migration guide for a comprehensive list of changes and step-by-step instructions.

This automated PR is a good starting point for the security fix, but it requires significant manual intervention to become functional.