The version 4.17.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 de1eb0ea71bfcf0861a4b9c8ab8f66a20032bd6e on greenkeeper/eslint-4.17.0 into 33a905612f7861d8190d71d5e244b20c9e69c0a3 on master.
Coverage remained the same at 100.0% when pulling de1eb0ea71bfcf0861a4b9c8ab8f66a20032bd6e on greenkeeper/eslint-4.17.0 into 33a905612f7861d8190d71d5e244b20c9e69c0a3 on master.
Coverage remained the same at 100.0% when pulling de1eb0ea71bfcf0861a4b9c8ab8f66a20032bd6e on greenkeeper/eslint-4.17.0 into 33a905612f7861d8190d71d5e244b20c9e69c0a3 on master.
Version 4.17.0 of eslint was just published.
The version 4.17.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 11 commits.
2af9446
4.17.0
5ad3fb2
Build: changelog update for 4.17.0
1da1ada
Update: Add "multiline" type to padding-line-between-statements (#8668)
bb213dc
Chore: Use messageIds in some of the core rules (#9648)
1aa1970
Docs: remove outdated rule naming convention (#9925)
3afaff6
Docs: Add prefer-destructuring variable reassignment example (#9873)
d20f6b4
Fix: Typo in error message when running npm (#9866)
51ec6a7
Docs: Use GitHub Multiple PR/Issue templates (#9911)
dc80487
Update: space-unary-ops uses astUtils.canTokensBeAdjacent (fixes #9907) (#9906)
084351b
Docs: Fix the messageId example (fixes #9889) (#9892)
9cbb487
Docs: Mention the
globals
key in the no-undef docs (#9867)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: