The version 3.14.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 3.14.1 of eslint just got published.
The version 3.14.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v3.14.1Commits
The new version differs by 29 commits .
e5446443.14.11297635Build: package.json and changelog update for 3.14.1791f32bFix: brace-style false positive for keyword method names (fixes #7974) (#7980)d7a0addDocs: Add ESLint tutorial embed to getting started (#7971)72d41f0Fix: no-var autofix syntax error in single-line statements (fixes #7961) (#7962)b9e5b68Fix: indent rule crash on sparse array with object (fixes #7959) (#7960)a7bd66aChore: Adding assign/redeclare tests to no-undefined (refs #7964) (#7965)8bcbf5dDocs: typo in prefer-promise-reject-errors (#7958)67ac93c3.14.02cf5810Build: package.json and changelog update for 3.14.0506324aFix:no-vardoes not fix if causes ReferenceError (fixes #7950) (#7953)05e7432New: no-chained-assignments rule (fixes #6424) (#7904)243e47dUpdate: Add fixer for no-else-return (fixes #7863) (#7864)f091d95New:prefer-promise-reject-errorsrule (fixes #7685) (#7689)ca01e00Fix: recognize all line terminators in func-call-spacing (fixes #7923) (#7924)There are 29 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: