[Snyk] Fix for 1 vulnerabilities

[Dustin4444]

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
	Prototype Pollution SNYK-JS-JSYAML-13961110	49

---

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

---

This change is 

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-89b49cc558ed77ae1ca813641d6aac2b

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, 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 resolving a critical 'Prototype Pollution' vulnerability. It achieves this by updating key development dependencies, eslint and lerna, in the package.json file. While the dependency versions are updated, a manual step is required to ensure the yarn.lock file is correctly synchronized, particularly for projects leveraging Yarn's zero-installs feature.

Highlights

• Vulnerability Fix: This pull request addresses and fixes one identified vulnerability, specifically a 'Prototype Pollution' issue (SNYK-JS-JSYAML-13961110) with a score of 49.
• Dependency Updates: The package.json file has been updated to upgrade eslint from version ^8.13.0 to ^9.0.0 and lerna from ^5 to ^8.1.9.
• Manual Intervention Required: A warning indicates that yarn.lock failed to update automatically and requires manual updating before merging, especially for users utilizing Yarn's zero-installs feature.

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 updates eslint and lerna to address a security vulnerability. However, these are major version upgrades that introduce significant breaking changes. More importantly, the yarn.lock file has not been updated, which is a critical issue that must be resolved manually. Before merging, you must run yarn install to update the lockfile and then migrate your configurations and code to be compatible with the new versions of ESLint and Lerna to avoid breaking your project.

[gemini-code-assist]

These dependency updates introduce major version bumps for eslint (v8 to v9) and lerna (v5 to v8), which come with significant breaking changes.

Critical Actions Required:

1. Update Lockfile: As noted in the PR description, yarn.lock has not been updated. You must run yarn install to update the lockfile. Without this, the vulnerability will not be fixed and your builds will not be reproducible.

2. Address Breaking Changes:

   • ESLint v9: This version introduces a new configuration system (eslint.config.js) and removes deprecated rules. You will likely need to migrate your .eslintrc configuration. Please consult the ESLint v9 migration guide.
   • Lerna v8: This is a major update from v5. You should review the Lerna changelogs for versions 6, 7, and 8 to understand the breaking changes and update your repository scripts and configuration accordingly.

Merging this PR without addressing these points will likely break your CI/CD pipeline and local development environments.