[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
	Symlink Following SNYK-JS-TARFS-13045213	541

---

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:

🦉 Symlink Following

[netlify]

❌ Error Happens

Name	Link
🔨 Latest commit	4b08eb7
🔍 Latest deploy log	https://app.netlify.com/projects/wekanhow/deploys/68dc1e8628bdfc0008ca464a

[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, aims to enhance the project's security posture by upgrading the gatsby dependency. The primary purpose of this upgrade is to mitigate a 'Symlink Following' vulnerability. Reviewers should be aware that a manual update of the yarn.lock file is necessary as the automated process encountered an issue.

Highlights

• Gatsby Dependency Upgrade: The gatsby dependency has been upgraded from version "1.0.0-beta.5-alpha.fb30fcd6" to "2.0.0" in package.json.
• Security Vulnerability Fix: This upgrade addresses a medium-severity 'Symlink Following' vulnerability (SNYK-JS-TARFS-13045213).
• Manual yarn.lock Update Required: The automated process failed to update the yarn.lock file, which will require a manual update before this pull request can be merged.

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 from Snyk upgrades Gatsby from a v1 pre-release to v2.0.0 to fix a security vulnerability. While this is a necessary security update, it's a major version upgrade that introduces significant breaking changes. The current state of the PR will break your application. I've added a critical comment on package.json detailing the additional changes required to make your project compatible with Gatsby v2, including updating React, Gatsby plugins, and refactoring code that uses deprecated Gatsby APIs.

[gemini-code-assist]

Upgrading Gatsby from v1 to v2 is a major update with significant breaking changes that will break your build. To successfully upgrade, you'll need to address several points:

• Update React: Gatsby v2 requires React v16. Your package.json lists react: "15.5.4". You need to update react and react-dom.

• Update Gatsby Plugins: All gatsby-* plugins must be updated to their v2-compatible versions. For example:

  • gatsby-plugin-google-analytics: ^1.0.1 is for v1.
  • gatsby-plugin-react-helmet: ^1.0.1 is for v1.
  • You also have local plugins (gatsby-plugin-sitemap, gatsby-plugin-typescript, gatsby-remark-prismjs) that are likely incompatible and will need to be updated or replaced.

• Remove gatsby-link: The gatsby-link component is now part of the core gatsby package. You should remove this dependency and update your imports from import Link from 'gatsby-link' to import { Link } from 'gatsby'. Your project uses a forked version, which further complicates this.

• Update Gatsby APIs: Gatsby v2 introduced API changes. You will need to update your code in files like gatsby-node.js, gatsby-browser.js, and gatsby-ssr.js. For example:

  • In gatsby-node.js, boundActionCreators is deprecated and replaced by actions.
  • In gatsby-browser.js, replaceComponentRenderer is removed and should be replaced with wrapRootElement.

• Update yarn.lock: As noted in the PR description, yarn.lock was not updated. You must run yarn to update it with the new dependencies after you've updated package.json.

I recommend consulting the official Gatsby v1 to v2 migration guide for a complete list of changes.