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 mkdirp-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.
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 8af3e74da75f5bcb901cd5f970b9db44b009d0b7 on greenkeeper-mkdirp-promise-5.0.1 into cc0892efd71bdeed443509b08423d7ff493d9c43 on master.
Hello lovely humans,
mkdirp-promise just published its new version 5.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 mkdirp-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:
GitHub Release
5.0.1 (2017-01-31)
Bug Fixes
The new version differs by 40 commits .
069da6b
fix(dependencies): change mkdirp to be a direct dependency
44b9731
mkdirp is not a peer dependency
355f115
Merge pull request #70 from ahmadnassri/greenkeeper/snazzy-6.0.0
74ab6b6
chore(package): update snazzy to version 6.0.0
9dcd076
Merge pull request #69 from ahmadnassri/greenkeeper/tap-9.0.2
b905cfe
chore(package): update tap to version 9.0.2
8e7f4fb
fix(modules): BREAKING CHANGE: module export path is now at
lib
e08ee6d
feat(compile): no longer requires babel, with node v4 Promises are finally native
1e92797
Merge pull request #65 from ahmadnassri/greenkeeper/babel-preset-env-1.0.2
ee5da22
chore(package): update babel-preset-env to version 1.0.2
4fc2a7e
Merge pull request #64 from ahmadnassri/greenkeeper/babel-preset-env-1.0.1
9030886
chore(package): update babel-preset-env to version 1.0.1
923d3a7
Merge pull request #63 from ahmadnassri/greenkeeper/babel-preset-env-1.0.0
e09e7c2
chore(package): update babel-preset-env to version 1.0.0
c591661
chore(package): update dependencies
There are 40 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.