Open greenkeeper[bot] opened 5 years ago
After pinning to 4.9.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
mock-fs was updated from 4.10.0
to 4.10.1
.Your tests are still failing with this version. Compare changes
devDependency
mock-fs was updated from 4.10.1
to 4.10.2
.Your tests are still failing with this version. Compare changes
devDependency
mock-fs was updated from 4.10.2
to 4.10.3
.Your tests are still failing with this version. Compare changes
devDependency
mock-fs was updated from 4.10.3
to 4.10.4
.Your tests are still failing with this version. Compare changes
The new version differs by 38 commits.
7f28122
4.10.4
7846c47
Log changes
19334ee
Merge pull request #281 from 3cp/fix-missing-promise-return
98ba9b6
Merge pull request #282 from niieani/fix-nested-access
9adc82f
fix: throw ENOTDIR when trying to open an incorrect path (nested under existing file)
994a529
fix: remove win32 file namespace prefix for fs.realpath.native and fs.promises.realpath
e63c109
chore: use path.toNamespacedPath when available
5284ba0
chore: clean up
16b9026
test: add test coverage to fs.promises.realpath and fs.realpathSync
4470222
test: add test coverage to fs.promises.lstat
17a2e12
test: add test coverage to fs.promises.readlink
8cf2098
test: add test coverage to fs.promises.link and fs.promises.symlink
bef86ed
test: add test coverage to fs.promises.utimes and filehandle.utimes
3353d00
test: add test coverage to fs.promises.unlink
259ad0b
chore: cleanup
There are 38 commits in total.
See the full diff
devDependency
mock-fs was updated from 4.10.4
to 4.11.0
.Your tests are still failing with this version. Compare changes
The devDependency mock-fs was updated from
4.9.0
to4.10.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mock-fs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β **continuous-integration/appveyor/branch:** AppVeyor build succeeded ([Details](https://ci.appveyor.com/project/Narazaka/nanikastorage/builds/24676235)). - β **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/Ikagaka/NanikaStorage/builds/534912427?utm_source=github_status&utm_medium=notification)).Commits
The new version differs by 5 commits.
0bbd60a
4.10.0
8475e4e
Log changes
e5586f6
Merge pull request #268 from 3cp/mkdir-recursive
d93b0b0
feat: support fs.mkdir recursive option for Node.js >=10.12.0
e436d85
test: turn on tests on nodejs v12
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: