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.
Coverage remained the same at 100.0% when pulling 6c24d7fdc356596aae557be16d4ae5506210809e on greenkeeper-mkdirp-promise-5.0.0 into cc0892efd71bdeed443509b08423d7ff493d9c43 on master.
Hello lovely humans,
mkdirp-promise just published its new version 5.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 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.0 (2016-12-13)
Bug Fixes
lib
(8e7f4fb1)Breaking Changes
module export path is now at
lib
no need for version specific exports
(8e7f4fb1)
The new version differs by 34 commits .
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
3c1c1aa
Merge pull request #62 from ahmadnassri/greenkeeper/babel-preset-env-0.0.9
b049a17
chore(package): update babel-preset-env to version 0.0.9
0343308
build(scripts): remove nyc dependency, use tap directly to generate coverage
a87361e
Merge pull request #61 from ahmadnassri/greenkeeper/echint-2.0.0
373d732
test(dependency): adding missing dependency
c3398ff
chore(package): update echint to version 2.0.0
There are 34 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade