[Snyk] Security upgrade eslint from 8.57.0 to 9.26.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
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	60

---

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.

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

• 🔍 Trigger a full review

✨ 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-eabdedb687779815d2c69ff2477dadf2

---

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, updates the eslint dependency to a newer version. The primary purpose is to resolve a known security vulnerability, thereby enhancing the project's overall security and code quality standards.

Highlights

• Dependency Upgrade: The eslint dependency has been upgraded from version 8.57.0 to 9.26.0.
• Security Fix: This upgrade addresses a 'Uncontrolled Recursion' vulnerability (SNYK-JS-ESLINT-15102420) found in the previous eslint version.
• Yarn Lock Warning: The yarn.lock file was not automatically updated by Snyk, requiring manual update for projects using Yarn's zero-install feature.

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

Changelog

• package.json
  • Updated the eslint dependency version from 8.57.0 to 9.26.0.

Activity

• This pull request was automatically created by Snyk to fix a security vulnerability.
• Snyk identified an 'Uncontrolled Recursion' vulnerability (SNYK-JS-ESLINT-15102420) in the eslint package.
• A warning was issued regarding the yarn.lock file not being updated, which may require manual intervention 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 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 eslint to fix a security vulnerability. While the security fix is important, this is a major version upgrade from v8 to v9, which introduces significant breaking changes. The project's ESLint configuration and plugins will need to be migrated to be compatible with ESLint v9, otherwise linting commands will likely fail. Additionally, as noted in the PR description, the yarn.lock file was not updated. You must run yarn to update the lockfile to ensure dependency consistency before merging.

[gemini-code-assist]

Upgrading eslint from version 8 to 9 is a major change with significant breaking changes. ESLint v9 introduced a new configuration system (flat config) and deprecated the old .eslintrc format.

Your project will likely require significant configuration changes to adapt to ESLint v9. This includes:

• Migrating your ESLint configuration to the new eslint.config.js format.
• Checking and potentially upgrading all ESLint plugins (eslint-config-prettier, eslint-plugin-import, eslint-plugin-jest, etc.) for compatibility with ESLint v9.
• Updating your linting scripts if they use deprecated CLI options.

Without these changes, your linting commands (yarn lint, yarn fix) are very likely to fail. Please refer to the ESLint v9 migration guide for detailed instructions.