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 fs-extra.
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 a3214191c7dd4144f92ecbcd8258ea7eb6a096e3 on greenkeeper-fs-extra-2.1.0 into a73f00e6ac119869267951e41b8d46d97feeb849 on master.
Hello lovely humans,
fs-extra just published its new version 2.1.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 fs-extra. 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 174 commits .
90b3609
2.1.0
6ebcb9c
Update CHANGELOG
efe0d80
Merge pull request #378 from jdalton/move-check
8d978db
Don't move when source and dest paths are the same.
cf2c50d
Merge pull request #386 from jprichardson/changelog
4db96c5
Update CHANGELOG
1f30161
Merge pull request #384 from jprichardson/docs-cleanup-async-methods
83a6190
docs: Refactor remove exmaple to use remove instead of removeSync
936011e
docs: Refactor remove and removeSync parameter name
fc5fca9
docs: Refactor docs to include parameters type
e46b820
Merge pull request #383 from jprichardson/docs-refactor-readJson-example
a4f6481
docs/readJson.md: Refactor example for readJson method, refactor move and moveSync tests descriptions
b5c72dc
Merge pull request #382 from jprichardson/docs-split-out-sync-methods
10756de
docs: Refactor readJsonSync example
02c2a62
Docs: Split out sync methods
There are 174 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.