The version 4.18.2 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).
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 4.18.2 of eslint was just published.
The version 4.18.2 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.18.2Commits
The new version differs by 12 commits.
22ff6f34.18.2817b84bBuild: changelog update for 4.18.26b71fd0Fix: table@4.0.2, because 4.0.3 needs "ajv": "^6.0.1" (#10022)3c697deChore: fix incorrect comment about linter.verify return value (#10030)9df8653Chore: refactor parser-loading out of linter.verify (#10028)f6901d0Fix: remove catastrophic backtracking vulnerability (fixes #10002) (#10019)e4f52ceChore: Simplify dataflow in linter.verify (#10020)33177cdChore: make library files non-executable (#10021)558ccbaChore: refactor directive comment processing (#10007)18e15d9Chore: avoid useless catch clauses that just rethrow errors (#10010)a1c3759Chore: refactor populating configs with defaults in linter (#10006)aea07dcFix: Make max-len ignoreStrings ignore JSXText (fixes #9954) (#9985)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: