-
Notifications
You must be signed in to change notification settings - Fork 60
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 🚨 #48
Comments
After pinning to 4.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
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 still failing with this version. Compare the changes 🚨 Release Notesv4.7.0
CommitsThe new version differs by 55 commits.
There are 55 commits in total. See the full diff |
Version 4.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.7.2CommitsThe new version differs by 7 commits.
See the full diff |
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.6.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.6.0Commits
The new version differs by 31 commits.
8f01a99
4.6.0
c0acbf2
Build: changelog update for 4.6.0
56dd769
Docs: fix link format in prefer-arrow-callback.md (#9198)
6becf91
Update: add eslint version to error output. (fixes #9037) (#9071)
0e09973
New: function-paren-newline rule (fixes #6074) (#8102)
88a64cc
Chore: Make parseJsonConfig() a pure function in Linter (#9186)
1bbac51
Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) (#9196)
3e8b70a
Fix: off-by-one error in eslint-disable comment checking (#9195)
73815f6
Docs: rewrite prefer-arrow-callback documentation (fixes #8950) (#9077)
0d3a854
Chore: avoid mutating report descriptors in report-translator (#9189)
2db356b
Update: no-unused-vars Improve message to include the allowed patterns (#9176)
8fbaf0a
Update: Add configurability to generator-star-spacing (#8985)
8ed779c
Chore: remove currentScopes property from Linter instances (refs #9161) (#9187)
af4ad60
Fix: Handle error when running init without npm (#9169)
4b94c6c
Chore: make parse() a pure function in Linter (refs #9161) (#9183)
There are 31 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: