Skip to content

[Snyk] Security upgrade eslint from 9.39.4 to 10.0.0 - #703

Open
qbey wants to merge 1 commit into
mainfrom
snyk-fix-b0107bf51b34f10418560a52ce089ab4
Open

[Snyk] Security upgrade eslint from 9.39.4 to 10.0.0#703
qbey wants to merge 1 commit into
mainfrom
snyk-fix-b0107bf51b34f10418560a52ce089ab4

Conversation

@qbey

@qbey qbey commented Sep 2, 2026

Copy link
Copy Markdown
Member

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • src/frontend/packages/eslint-config-conversations/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
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-JSYAML-19496768
  710  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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:

🦉 Allocation of Resources Without Limits or Throttling

…o reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-JSYAML-19496768
@qbey

qbey commented Sep 2, 2026

Copy link
Copy Markdown
Member Author

Merge Risk: High

This major upgrade from ESLint v9 to v10 introduces significant and mandatory breaking changes, most notably the complete removal of the legacy .eslintrc configuration system.

Key Breaking Changes:

  • eslintrc Configuration Removed: Support for .eslintrc.* and .eslintignore files has been completely removed. You must migrate to the new flat configuration format (eslint.config.js). CLI arguments related to the old config system like --env and --rulesdir are also removed.
  • Node.js Version Requirement: Support for Node.js versions older than v20.19.0 has been dropped. You must ensure your environment is running a supported Node.js version.
  • New Config File Lookup: The configuration file (eslint.config.js) is now located by searching up from the directory of each linted file, which is a change from the previous behavior of using the current working directory.
  • JSX Reference Tracking: ESLint now correctly tracks scope for JSX elements. This may lead to new no-unused-vars or no-undef errors in your codebase that need to be fixed.
  • eslint-env Comments are Errors: Using /* eslint-env */ comments will now cause a linting error. This configuration must be moved into your eslint.config.js file.

Recommendation: This upgrade requires a mandatory migration of your entire ESLint configuration from the legacy .eslintrc format to the new eslint.config.js flat config. This is a significant effort and should be handled carefully by following the official migration guide.

Source: ESLint v10.0.0 Release Notes, Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

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.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Team

Run ID: f136d80f-3c7e-4ff7-ab96-35dd61bacf37

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

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

sonarqubecloud Bot commented Sep 2, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants