-
Notifications
You must be signed in to change notification settings - Fork 16
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 🚨 #32
Comments
After pinning to 4.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.4.0
CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Version 4.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.4.1 |
Version 4.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.5.0
CommitsThe new version differs by 12 commits.
See the full diff |
Version 4.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.6.0
CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Version 4.6.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.6.1
CommitsThe new version differs by 6 commits.
See the full diff |
Version 4.7.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv4.7.0
|
Version 4.3.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.3.0peerDependencies
package.json snippet valid JSON (#8971) (Sam Adams)output: null
to assert that a test case is not autofixed. (#8960) (薛定谔的猫)indent
test (#8925) (Teddy Katz)indent
internals (#8947) (Teddy Katz)indent
rule (#8905) (Teddy Katz)indent
(#8926) (Teddy Katz)allowAtRootLevel
option (fixes #8902) (#8906) (Teddy Katz)Commits
The new version differs by 28 commits.
2874d75
4.3.0
1c83662
Build: changelog update for 4.3.0
91dccdf
Update: support more options in prefer-destructuring (#8796)
3bebcfd
Update: Support generator yields in no constant condition (#8762)
96df8c9
Fix: Handle fixing objects containing comments (fixes #8484) (#8944)
e39d41d
Docs: Make
peerDependencies
package.json snippet valid JSON (#8971)a5fd101
Fix: duplicated error message if a crash occurs (fixes #8964) (#8965)
f8d122c
Docs: trailing commas not allowed in json (#8969)
d09288a
Chore: Use
output: null
to assert that a test case is not autofixed. (#8960)e639358
Update: add question to confirm downgrade (fixes #8870) (#8911)
601039d
Docs: fix badge in eslint-config-eslint readme (#8954)
3c231fa
Update: add enforceInMethodNames to no-underscore-dangle (fixes #7065) (#7234)
128591f
Update: prefer-numeric-literals warns Number.parseInt (fixes #8913) (#8929)
846f8b1
Docs: Clarified that core PRs require issue in maintainer guide (#8927)
55bc35d
Fix: Avoid shell mangling during eslint --init (#8936)
There are 28 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: