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-plugin-promise.
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 45f9160847bea4ee109bad75c6b4e7702438592a on greenkeeper-eslint-plugin-promise-2.0.0 into 184ed35dd3718b2e3df4586070f98cb3d0c5872a on master.
Coverage remained the same at 100.0% when pulling 66551bbf5bf3b0498ed074009d014216f3016530 on greenkeeper-eslint-plugin-promise-2.0.0 into a9a123ad294a719c42b5f4f82e326c3683d708d4 on master.
Coverage remained the same at 100.0% when pulling 7d55da691c5d0e41749c2d2d1e1497ac5d64ba43 on greenkeeper-eslint-plugin-promise-2.0.0 into ddf5548885d306a3d78ff3088408c4ddab18f1fa on master.
Coverage remained the same at 100.0% when pulling 3fa495dae8488af9739d21de53451d3986d99ff1 on greenkeeper-eslint-plugin-promise-2.0.0 into 4b7dc6813bcae3d3b679fed47afd82dd8b48f390 on master.
Hello lovely humans,
eslint-plugin-promise just published its new version 2.0.0.
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-plugin-promise. 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:
The new version differs by 21 commits .
4447aec
2.0.0
9748ea9
updated changelog
dc0d063
Merge pull request #19 from jokeyrhyme/bump-deps-eslint-3
083dc3e
bumps deps; use ESLint 3 rule format
d6bd2a0
1.3.2
bb1ed7e
updated tests to eslint 2.0
782b7f2
Merge pull request #16 from lparry/lparry/fix-no-native-scope
524d0a1
Added changelog (fixes #17)
9c77fe1
Make no-native work with eslint 2 too
fa60b28
1.3.1
6944fb4
Merge pull request #15 from lparry/fix-no-native
e771551
Actually include no-native in the rules
c7f6588
1.3.0
04c7005
no-native rule
7b96139
1.2.0
There are 21 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade