This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 100.0% when pulling c205d746daca59e110e0886076039445564dcc71 on greenkeeper-eslint-3.0.1 into a44d2019732bcbc5fa6d318ba173ba9d394c382c on master.
Coverage remained the same at 100.0% when pulling b6fadd55962a5fb1332f2a9056565e1c2eca981d on greenkeeper-eslint-3.0.1 into 184ed35dd3718b2e3df4586070f98cb3d0c5872a on master.
Hello lovely humans,
eslint just published its new version 3.0.1.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
no-unused-vars
false positive around callback (fixes #6576) (#6579) (Toru Nagashima)no-unused-vars
ignore for-in (fixes #2342) (#6126) (Oleg Gaidarenko)outerIIFEBody
inindent
(fixes #6581) (#6584) (alberto)max-len
(fixes #6564) (#6565) (not-an-aardvark)The new version differs by 373 commits .
0fd4b6d
3.0.1
ebf2987
Build: package.json and changelog update for 3.0.1
27700cf
Fix:
no-unused-vars
false positive around callback (fixes #6576) (#6579)124d8a3
Docs: Pull request template (#6568)
e9a2ed9
Docs: Fix rules\id-length exceptions typos (fixes #6397) (#6593)
a2cfa1b
Fix: Make outerIIFEBody work correctly (fixes #6585) (#6596)
9c451a2
Docs: Use string severity in example (#6601)
8308c0b
Chore: remove path-is-absolute in favor of the built-in (fixes #6598) (#6600)
7a63717
Docs: Add missing pull request step (fixes #6595) (#6597)
de3ed84
Fix: make
no-unused-vars
ignore for-in (fixes #2342) (#6126)6ef2cbe
Fix: strip Unicode BOM of config files (fixes #6556) (#6580)
ee7fcfa
Docs: Correct type of
outerIIFEBody
inindent
(fixes #6581) (#6584)25fc7b7
Fix: false negative of
max-len
(fixes #6564) (#6565)f6b8452
Docs: Distinguish examples in rules under Stylistic Issues part 6 (#6567)
5ec54be
3.0.0
There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade