The version 4.18.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 aece483f98ec19bd692a8e023dd6fc81b99c31a8 on greenkeeper/eslint-4.18.0 into 2858738cf82bd2341f92bae839e6a39891e471de on master.
Coverage remained the same at 100.0% when pulling aece483f98ec19bd692a8e023dd6fc81b99c31a8 on greenkeeper/eslint-4.18.0 into 2858738cf82bd2341f92bae839e6a39891e471de on master.
Coverage remained the same at 100.0% when pulling aece483f98ec19bd692a8e023dd6fc81b99c31a8 on greenkeeper/eslint-4.18.0 into 2858738cf82bd2341f92bae839e6a39891e471de on master.
Version 4.18.0 of eslint was just published.
The version 4.18.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.
Commits
The new version differs by 14 commits.
883a2a2
4.18.0
89d55ca
Build: changelog update for 4.18.0
70f22f3
Chore: Apply memoization to config creation within glob utils (#9944)
0e4ae22
Update: fix indent bug with binary operators/ignoredNodes (fixes #9882) (#9951)
47ac478
Update: add named imports and exports for object-curly-newline (#9876)
e8efdd0
Fix: support Rest/Spread Properties (fixes #9885) (#9943)
f012b8c
Fix: support Async iteration (fixes #9891) (#9957)
74fa253
Docs: Clarify no-mixed-operators options (fixes #9962) (#9964)
426868f
Docs: clean up key-spacing docs (fixes #9900) (#9963)
4a6f22e
Update: support eslint-disable-* block comments (fixes #8781) (#9745)
777283b
Docs: Propose fix typo for function (#9965)
bf3d494
Docs: Fix typo in max-len ignorePattern example. (#9956)
d64fbb4
Docs: fix typo in prefer-destructuring.md example (#9930)
f8d343f
Chore: Fix default issue template (#9946)
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: