-
Notifications
You must be signed in to change notification settings - Fork 133
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
An in-range update of eslint is breaking the build 🚨 #251
Comments
After pinning to 4.16.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.18.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 14 commits.
See the full diff |
Version 4.18.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 5 commits.
See the full diff |
Version 4.18.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.18.2
CommitsThe new version differs by 12 commits.
See the full diff |
Version 4.19.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.19.0
CommitsThe new version differs by 12 commits.
See the full diff |
Version 4.19.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.19.1
CommitsThe new version differs by 7 commits.
See the full diff |
Version 4.17.0 of eslint was just published.
This version is covered by your current version range and after updating it in your project the build failed.
eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 11 commits.
2af9446
4.17.0
5ad3fb2
Build: changelog update for 4.17.0
1da1ada
Update: Add "multiline" type to padding-line-between-statements (#8668)
bb213dc
Chore: Use messageIds in some of the core rules (#9648)
1aa1970
Docs: remove outdated rule naming convention (#9925)
3afaff6
Docs: Add prefer-destructuring variable reassignment example (#9873)
d20f6b4
Fix: Typo in error message when running npm (#9866)
51ec6a7
Docs: Use GitHub Multiple PR/Issue templates (#9911)
dc80487
Update: space-unary-ops uses astUtils.canTokensBeAdjacent (fixes #9907) (#9906)
084351b
Docs: Fix the messageId example (fixes #9889) (#9892)
9cbb487
Docs: Mention the
globals
key in the no-undef docs (#9867)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: