The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling bf18ae2c74d39cec731c8146243694e709986e0e on greenkeeper/eslint-5.0.0 into 0036e443edb8d1bfe468de45fcbf9240db5b2ba5 on master.
Coverage remained the same at 100.0% when pulling bf18ae2c74d39cec731c8146243694e709986e0e on greenkeeper/eslint-5.0.0 into 0036e443edb8d1bfe468de45fcbf9240db5b2ba5 on master.
Coverage remained the same at 100.0% when pulling bf18ae2c74d39cec731c8146243694e709986e0e on greenkeeper/eslint-5.0.0 into 0036e443edb8d1bfe468de45fcbf9240db5b2ba5 on master.
Version 5.0.0 of eslint was just published.
[eslint](https://github.com/eslint/eslint)
The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v5.0.0Release blogpost
Migration guide
Commits
The new version differs by 148 commits.
36ced0a
5.0.0
5fd5632
Build: changelog update for 5.0.0
0feedfd
New: Added max-lines-per-function rule (fixes #9842) (#10188)
daefbdb
Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500)
077358b
Docs: no-process-exit: recommend process.exitCode (#10478)
f93d6ff
Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476)
05343fd
Fix: add parens for yield statement (fixes #10432) (#10468)
d477c5e
Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470)
7a7580b
Update: Add considerPropertyDescriptor option to func-name-matching (#9078)
e0a0418
Fix: crash on optional catch binding (#10429)
de4dba9
Docs: styling team members (#10460)
5e453a3
Docs: display team members in tables. (#10433)
b1895eb
Docs: Restore intentional spelling mistake (#10459)
a9da57d
5.0.0-rc.0
3ac3df6
Build: changelog update for 5.0.0-rc.0
There are 148 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: