Skip to content

chore(deps): update eslint monorepo to v10 (major) #1521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update eslint monorepo to v10 (major) #1521

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,12 +64,12 @@
"@babel/plugin-transform-modules-commonjs": "^7.26.3",
"@babel/preset-env": "^7.26.9",
"@babel/preset-typescript": "^7.27.0",
"@eslint/js": "^9.37.0",
"@eslint/js": "^10.0.0",
"@types/jest": "^30.0.0",
"@types/node": "~20",
"@typescript-eslint/parser": "^8.46.0",
"babel-jest": "^30.2.0",
"eslint": "^9.37.0",
"eslint": "^10.0.0",
Copy link
Contributor

@greptile-apps greptile-apps bot Mar 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing lockfile update

The package-lock.json was not updated as part of this PR. Without a lockfile update, npm install will attempt to resolve eslint@^10.0.0 and @eslint/js@^10.0.0 at install time, which may lead to inconsistent CI builds. The lockfile currently still pins eslint@9.39.2. This PR should include a regenerated package-lock.json to ensure deterministic installs.

"eslint-plugin-jest": "^29.0.1",
"eslint-plugin-n": "^17.23.1",
"iron-webcrypto": "^2.0.0",
Expand Down
Loading