[Snyk] Fix for 3 vulnerabilities

[saurabharch]

Snyk has created this PR to fix 3 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
	Directory Traversal SNYK-JS-TAR-15032660	693
	Prototype Pollution SNYK-JS-LODASH-15053838	631
	Prototype Pollution SNYK-JS-LODASHES-15053836	631

---

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:

🦉 Prototype Pollution
🦉 Directory Traversal

[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 improve the project's security by resolving three medium-severity vulnerabilities. It achieves this by upgrading several key dependencies listed in the package.json file. Reviewers should be aware that a manual update of the yarn.lock file is necessary to complete the fix.

Highlights

• Vulnerability Fixes: This pull request addresses three medium-severity vulnerabilities identified by Snyk: a Directory Traversal issue (SNYK-JS-TAR-15032660) and two Prototype Pollution vulnerabilities (SNYK-JS-LODASH-15053838, SNYK-JS-LODASHES-15053836).
• Dependency Upgrades: To mitigate the identified vulnerabilities, several dependencies in package.json have been upgraded to their latest secure versions, including gatsby, lodash, postcss-cssnext, postcss-inherit, relay-compiler, and sharp.
• Yarn Lock Warning: A warning is present indicating that the yarn.lock file was not automatically updated by Snyk and requires manual updating before this pull request can be merged.

🧠 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. ↩

[netlify]

❌ Error Happens

Name	Link
🔨 Latest commit	4837349
🔍 Latest deploy log	https://app.netlify.com/projects/wekanhow/deploys/697939b60fb1b70008057f71

[gemini-code-assist]

Code Review

This pull request from Snyk aims to fix security vulnerabilities by updating dependencies. While this is important, please be aware that this PR introduces several major version upgrades which are breaking changes. Specifically, gatsby is updated from v1 to v2, and relay-compiler from v1 to v2. These upgrades require significant manual code migration and will break your application if merged without the necessary changes.

Furthermore, the PR description notes that yarn.lock has not been updated. You must run yarn (or yarn install) to update the lockfile and commit it to ensure the dependency changes are applied.

I recommend treating this PR as a guide for what needs to be updated, and to carefully plan the migration for each major version bump, starting with the official migration guides.

[gemini-code-assist]

Upgrading Gatsby from v1 to v2 is a major undertaking with many breaking changes. Your application will not work after merging this without a thorough migration. Please follow the official Gatsby v1 to v2 migration guide.

[gemini-code-assist]

This major version upgrade of relay-compiler from v1 to v2 is likely to have breaking changes that will require code modifications.

[gemini-code-assist]

This is a major version bump. Also, please note that postcss-cssnext is deprecated. The recommended replacement is postcss-preset-env. You should consider migrating to it for better long-term support.

[gemini-code-assist]

Switching from a git URL to a versioned package is a good practice. However, this appears to be a major version change. Be aware that there may be breaking changes that require code adjustments.