Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAn in-range update of eslint is breaking the build 🚨 #1154
Comments
greenkeeper
bot
added
the
greenkeeper
label
Jun 23, 2018
This comment has been minimized.
This comment has been minimized.
|
After pinning to 5.0.0-rc.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
This comment has been minimized.
This comment has been minimized.
Version 5.0.1 just got published.Your tests are still failing with this version. Compare the changes Release Notesv5.0.1 |
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
Sep 24, 2018
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
label
Sep 24, 2018
stale
bot
closed this
Oct 1, 2018
lock
bot
locked as resolved and limited conversation to collaborators
Dec 30, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
greenkeeper bot commentedJun 23, 2018
Version 5.0.0 of eslint was just published.
[eslint](https://github.com/eslint/eslint)This version is covered by your current version range and after updating it in your project the build failed.
eslint is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Release Notes
v5.0.0Release blogpost
Migration guide
Commits
The new version differs by 13 commits.
36ced0a5.0.05fd5632Build: changelog update for 5.0.00feedfdNew: Added max-lines-per-function rule (fixes #9842) (#10188)daefbdbUpgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500)077358bDocs: no-process-exit: recommend process.exitCode (#10478)f93d6ffFix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476)05343fdFix: add parens for yield statement (fixes #10432) (#10468)d477c5eFix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470)7a7580bUpdate: Add considerPropertyDescriptor option to func-name-matching (#9078)e0a0418Fix: crash on optional catch binding (#10429)de4dba9Docs: styling team members (#10460)5e453a3Docs: display team members in tables. (#10433)b1895ebDocs: Restore intentional spelling mistake (#10459)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🌴