The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of fs-extra.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 30dbff31c26389c8412cdc8d2b9cf532674012c3 on greenkeeper/fs-extra-5.0.0 into b6869fbfc71499efbe3308203c200b9f35d7d96d on master.
Version 5.0.0 of fs-extra was just published.
The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of fs-extra.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 22 commits.
80494ee
5.0.0
1212680
Merge branch 'develop'
42e42be
Merge pull request #521 from jprichardson/async-filter
a06f88b
Apply the async filter to initial filter checking in copy
86d2ad6
Merge pull request #519 from jprichardson/rewrite-copySync
5bdbdc4
Skip copySync preserveTimestamp tests on older node versions
935e189
Merge pull request #518 from jprichardson/async-filter
9732252
Allow copy's filter to return a Promise
5d1f2d3
Use fs.chmodSync() before preserveTimestamp
d6f6da1
Use srcStat param in copyFileFallback
546216c
Remove setTimeout when preserveTimestamp is true
fda912a
Rewrite copySync, add more tests, remove fixtures folder
03fba97
Merge pull request #517 from jprichardson/copy-parent-dir
199ec9f
Apply filter before creating parent dir in copy
b72ba64
Merge pull request #516 from jprichardson/fix-copy-streams
There are 22 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: