[Snyk] Security upgrade eslint from 8.57.0 to 9.0.0

[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	50

---

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

[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-6927416afdc1b3fbfe3bc443e0f5332e

---

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 focuses on enhancing the project's security posture by upgrading the "eslint" dependency to its latest major version, "9.0.0". This automated update, initiated by Snyk, is crucial for mitigating an identified "Prototype Pollution" vulnerability, ensuring the codebase remains secure against known exploits.

Highlights

• Dependency Upgrade: Upgraded the "eslint" package from version "8.57.0" to "9.0.0".
• Security Fix: This upgrade addresses a "Prototype Pollution" vulnerability (SNYK-JS-JSYAML-13961110) with a severity score of 50.
• 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 automatically and requires manual intervention before merging.
• Zero-Install Note: Users leveraging Yarn's zero-installs feature will need to run "yarn" to update the ".yarn/cache" directory.

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 PR upgrades ESLint from v8 to v9 to fix a security vulnerability. This is a major version bump that introduces significant breaking changes. You will likely need to migrate your ESLint configuration to the new 'flat config' format (eslint.config.js), update related ESLint plugins, and regenerate the yarn.lock file. Without these changes, your linting process is likely to fail.

[gemini-code-assist]

Upgrading ESLint to a new major version (v8 to v9) introduces significant breaking changes that will require further updates to the project.

Here are the key actions you'll likely need to take:

1. Migrate to Flat Config: ESLint v9 has deprecated the .eslintrc configuration file format. You will need to migrate your configuration to the new flat config format (eslint.config.js). You can find the migration guide in the official ESLint documentation.

2. Update ESLint Plugins: Other ESLint plugins may need to be updated to be compatible with v9. You should check the compatibility of packages like eslint-plugin-import and eslint-plugin-jest and update them if necessary.

3. Update yarn.lock: As mentioned in the PR description, the yarn.lock file needs to be regenerated. Please run yarn install to update it.

Failing to address these points will likely cause your linting tasks to fail.