-
Notifications
You must be signed in to change notification settings - Fork 30k
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.
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
tools: update ESLint to 5.3.0 #22134
Conversation
Since the lite CI runs the linter and none of the other jobs in node-test-pull-request touch this code, the lite CI is probably sufficient here. |
Test failure is a known flaky (#21038). |
@nodejs/linting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if CI is green
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
Landed in 6ad12d4 |
PR-URL: nodejs#22134 Reviewed-By: Bryan English <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Jon Moss <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
PR-URL: #22134 Reviewed-By: Bryan English <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Jon Moss <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
Since we made some efforts to make the ESLint updates in Node.js core a little bit less churn-y, maybe we can do more frequent smaller updates like this? (Or maybe it's still too churn-y?)
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes