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 all-contributors-cli.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 100.0% when pulling 96d2b791e65419b2682ac059d985e5442458857f on greenkeeper-all-contributors-cli-4.0.0 into a73f00e6ac119869267951e41b8d46d97feeb849 on master.
Hello lovely humans,
all-contributors-cli just published its new version 4.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 all-contributors-cli. 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
4.0.0 (2017-02-15)
Bug Fixes
Breaking Changes
Drop support for Node < v4. This uses native Promises available from Node v4.
fix: Bump inquirer to v3.0.1. Fixes #33 to improve Windows support.
refactor: Promisify everything as inquirer uses Promises from 1.0.0 onwards
(1305a7cd)
The new version differs by 9 commits .
1305a7c
fix: Bump inquirer to v3 and promisify everything (#34)
1e73194
fix: exit process on success to continue execution of othe scripts (#32)
cc61913
docs(README): Added some general improvements. (#30)
71f594c
docs(readme): update README.md (#29)
4860f38
feat: semantic-release (#28)
1c97ba2
chore: semantic-release
8fd4098
feat(types): add/update contrib types (#24)
806894e
3.0.7
190813c
Show a helpful message when .all-contributorsrc doesn't exist. (#23)
See the full diff.
Screencast
Try it today. Free for private repositories during beta.