-
Notifications
You must be signed in to change notification settings - Fork 1
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 🚨 #10
Comments
After pinning to 4.6.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.7.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.7.1 |
Version 4.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.7.2 |
Version 4.8.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.8.0
CommitsThe new version differs by 14 commits.
See the full diff |
Version 4.9.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.9.0
CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Version 4.10.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.10.0
CommitsThe new version differs by 38 commits.
There are 38 commits in total. See the full diff |
Version 4.11.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.11.0
CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Version 4.12.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.12.0
CommitsThe new version differs by 15 commits.
See the full diff |
Version 4.12.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.12.1 |
Version 4.13.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.13.0
CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.13.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.13.1
CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.14.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.14.0
CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Version 4.15.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.15.0
CommitsThe new version differs by 14 commits.
See the full diff |
Version 4.16.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.16.0
CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 4.17.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 11 commits.
See the full diff |
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 5.0.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.0.0
CommitsThe new version differs by 148 commits.
There are 148 commits in total. See the full diff |
Version 5.0.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.0.1 |
Your tests are still failing with this version. Compare changes Release Notes for v5.14.0
CommitsThe new version differs by 273 commits.
There are 250 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.14.1 |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.0
CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.1 |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.2
CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v5.15.3 |
Your tests are still failing with this version. Compare changes Release Notes for v5.16.0
CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.0.0
CommitsThe new version differs by 134 commits.
There are 134 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.0.1
CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.1.0
CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.2.0
CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.2.1CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.2.2 |
Your tests are still failing with this version. Compare changes Release Notes for v6.3.0
CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.4.0
CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.5.0
CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.5.1CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.6.0
CommitsThe new version differs by 53 commits.
There are 53 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.7.0
CommitsThe new version differs by 49 commits.
There are 49 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.7.1 |
Your tests are still failing with this version. Compare changes Release Notes for v6.7.2
CommitsThe new version differs by 8 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v6.8.0
CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Version 4.7.0 of eslint just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v4.7.0node.parent
is already set (fixes #9122) (#9283) (Teddy Katz)return
(fixes #9285) (#9296) (Teddy Katz)npm run perf
description (#9274) (Teddy Katz)Commits
The new version differs by 55 commits.
439e8e6
4.7.0
2ec62f9
Build: changelog update for 4.7.0
787b78b
Upgrade: Espree v3.5.1 (fixes #9153) (#9314)
1488b51
Update: run rules after
node.parent
is already set (fixes #9122) (#9283)4431d68
Docs: fix wrong config in max-len example. (#9309)
9d1df92
Chore: Revert "avoid handling Rules instances in config-validator" (#9295)
7d24dde
Docs: Fix code snippet to refer to the correct option (#9313)
12388d4
�Chore: rewrite parseListConfig for a small perf gain. (#9300)
ce1f084
Update: fix MemberExpression handling in no-extra-parens (fixes #9156)
0c720a3
Update: allow autofixing when using processors (fixes #7510) (#9090)
838df76
Chore: upgrade deps. (#9289)
f12def6
Update: indent flatTernary option to handle
return
(fixes #9285) (#9296)e220687
Fix: remove autofix for var undef inits (fixes #9231) (#9288)
002e199
Docs: fix no-restricted-globals wrong config. (#9305)
fcfe91a
Docs: fix wrong config in id-length example. (#9303)
There are 55 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: