The version 4.10.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 Notesv4.10.0
bb6e60a Fix: Improve the doc for no-restricted-modules rule (fixes #9437) (#9495) (vibss2397)
c529de9 Docs: Amend rule document to correct and complete it (refs #6251). (#9498) (Jonathan Pool)
f9c6673 Chore: Add tests to cover array and object values and leading commas. (#9502) (Jonathan Pool)
9169258 Chore: remove npm run check-commit script (#9513) (Teddy Katz)
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 b9e54f3478e353fd4a6df490ad4fde6490941d28 on greenkeeper/eslint-4.10.0 into 30d3d312cffe04154ffc594ce788f34fb73796d2 on master.
Version 4.10.0 of eslint was just published.
The version 4.10.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
v4.10.0npm run check-commit
script (#9513) (Teddy Katz).md
to link (for github users) (#9501) (薛定谔的猫)npm run profile
script (fixes #9397) (#9455) (Teddy Katz)Commits
The new version differs by 38 commits.
9deb1b1
4.10.0
6d19001
Build: changelog update for 4.10.0
bb6e60a
Fix: Improve the doc for no-restricted-modules rule (fixes #9437) (#9495)
c529de9
Docs: Amend rule document to correct and complete it (refs #6251). (#9498)
f9c6673
Chore: Add tests to cover array and object values and leading commas. (#9502)
9169258
Chore: remove
npm run check-commit
script (#9513)7d390b2
Docs: Revise contributor documentation on issue labels. (#9469)
d80b9d0
Fix: no-var don't fix globals (fixes #9520) (#9525)
b8aa071
Fix: allow linting the empty string from stdin (fixes #9515) (#9517)
350a72c
Chore: regex.test => string.startsWith (#9518)
de0bef4
Chore: remove obsolete eslintbot templates (#9512)
720b6d5
Docs: Update ISSUE_TEMPLATE.md (#9504)
2fa64b7
Fix: should not convert non-consecutive line comments to a single blo… (#9475)
9725146
Fix: multiline-comment-style fix produces invalid code (fixes #9461). (#9463)
b12cff8
Fix: Expected order of jsdoc tags (fixes #9412) (#9451)
There are 38 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: