chore(deps-dev): bump eslint from 8.57.0 to 9.26.0#3797
chore(deps-dev): bump eslint from 8.57.0 to 9.26.0#3797dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
| "cross-env": "7.0.2", | ||
| "deep-object-diff": "^1.1.9", | ||
| "eslint": "^8.12.0", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
ESLint 9 requires @typescript-eslint v8, but v5/v6 remain
High Severity
Upgrading eslint from v8 to v9.26.0 without updating @typescript-eslint/eslint-plugin and @typescript-eslint/parser creates a peer dependency incompatibility. ESLint 9.x requires @typescript-eslint/* v8+, but the packages remain at v5.x (backend, services) and v6.x (github actions). This will cause linting to fail or behave incorrectly since the typescript-eslint packages don't support ESLint 9's APIs and flat config system.
Additional Locations (2)
| "cross-env": "7.0.2", | ||
| "deep-object-diff": "^1.1.9", | ||
| "eslint": "^8.12.0", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
ESLint 9 incompatible with eslint-config-airbnb packages
High Severity
The eslint-config-airbnb-base: ^15.0.0 and eslint-config-airbnb-typescript: ^16.1.4 packages do not support ESLint 9.x. These configs use the legacy eslintrc format and rules that are incompatible with ESLint 9's new configuration system. The Airbnb team has not released ESLint 9-compatible versions, so linting in the backend will fail even after addressing the @typescript-eslint incompatibility.
| "@typescript-eslint/eslint-plugin": "^5.59.2", | ||
| "@typescript-eslint/parser": "^5.59.2", | ||
| "eslint": "^8.39.0", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
ESLint 9 removes --ext CLI option used in service lint scripts
Medium Severity
The upgrade to eslint: ^9.26.0 in the services workspace will break lint scripts in multiple service apps (cache_worker, categorization_worker, cron_service, data_sink_worker, entity_merging_worker) that use npx eslint --ext .ts src. The --ext CLI option was removed in ESLint 9 and will cause an "Unknown option '--ext'" error when running lint commands. These apps don't have their own eslint dependency and rely on the workspace root version.
375d408 to
7812489
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
| "cross-env": "7.0.2", | ||
| "deep-object-diff": "^1.1.9", | ||
| "eslint": "^8.12.0", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
ESLint 9 won't find legacy .eslintrc config files
High Severity
ESLint 9 uses flat config (eslint.config.js) by default and no longer automatically discovers .eslintrc.* files. The codebase has backend/.eslintrc.js, services/.eslintrc.cjs, and .github/actions/node/.eslintrc.cjs but no flat config files anywhere. Running eslint . (the backend lint script) will fail because ESLint 9 can't find a config. No migration to flat config or ESLINT_USE_FLAT_CONFIG=false workaround was added.
Additional Locations (2)
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
7812489 to
2457c6d
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
3 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
| "cross-env": "7.0.2", | ||
| "deep-object-diff": "^1.1.9", | ||
| "eslint": "^8.12.0", | ||
| "eslint": "^9.26.0", |
There was a problem hiding this comment.
ESLint 9 incompatible with existing plugin ecosystem
High Severity
Bumping eslint from v8 to v9 is a major version upgrade with breaking changes, but none of the dependent plugins or configs were updated. @typescript-eslint/eslint-plugin v5 (backend/services) and v6 (.github/actions/node) only support ESLint ^6 || ^7 || ^8. Similarly, eslint-config-airbnb-base v15, eslint-config-airbnb-typescript v16, and eslint-plugin-import v2.29.1 don't support ESLint 9. The project also has no eslint.config.js (flat config), which ESLint 9 requires by default, and multiple service lint scripts use the removed --ext CLI flag. This will break linting across the entire project.
Additional Locations (2)
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2457c6d to
4845270
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
4845270 to
cd940d3
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
cd940d3 to
6e4c976
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
6e4c976 to
672dc8c
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
4 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
Bumps [eslint](https://github.com/eslint/eslint) from 8.57.0 to 9.26.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Changelog](https://github.com/eslint/eslint/blob/v9.26.0/CHANGELOG.md) - [Commits](eslint/eslint@v8.57.0...v9.26.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 9.26.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
672dc8c to
fb3570c
Compare
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
3 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |


Bumps eslint from 8.57.0 to 9.26.0.
Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
8bbabc49.26.016f5ff7Build: changelog update for 9.26.05b247c8chore: upgrade to@eslint/js@9.26.0(#19681)d6fa4acchore: package.json update for@eslint/jsreleasee9754e7feat: add reportGlobalThis to no-shadow-restricted-names (#19670)0fa2b7afeat: add suggestions foreqeqeqrule (#19640)dd98d63docs: Update README96e84defix: check cache file existence before deletion (#19648)c25e858docs: Update README0958690chore: disambiguate internal typesLanguageOptionsandRule(#19669)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Note
Medium Risk
ESLint v9 is a major version bump that can change lint rule behavior and CI/lint-staged outcomes across multiple workspaces, but it doesn’t alter production runtime logic.
Overview
Upgrades dev tooling by bumping
eslintto^9.26.0in the GitHub Action (.github/actions/node),backend, andservicespackages.Refreshes
pnpm-lock.yamlto reflect the ESLint v9 dependency graph (notably new@eslint/*packages and updated@typescript-eslint/*peer resolutions), with no runtime application code changes.Written by Cursor Bugbot for commit fb3570c. This will update automatically on new commits. Configure here.