An in-range update of graceful-fs is breaking the build π¨
greenkeeper opened this issue Β· comments
The dependency graceful-fs was updated from 4.1.11
to 4.1.12
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
graceful-fs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Commits
The new version differs by 14 commits.
845e073
4.1.12
e2c4556
auto-publish scripts
ee41b4c
declare officially supported node versions, >=6
97a4e64
remove deprecated Buffer ctor from tests
2b3409f
update tap, fix audit notices
dfe2d43
don't patch streams unless they exist
9b47ebe
indentation consistency
2464ad3
travis: only LTS node versions, test on windows
19c8372
remove node 0.10, tap doesn't support it.
7118018
fix Cannot find module '../' in old node
8aadab7
use math.pow instead of **
62bddf0
fix memory leaks, includes test to make sure fix is working
1bf2345
fix memory leaks, includes test to make sure fix is working
654d5a2
use newer tap
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
- The
dependency
graceful-fs was updated from4.1.12
to4.1.13
.
Your tests are still failing with this version. Compare changes
After pinning to 4.1.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
dependency
graceful-fs was updated from4.1.13
to4.1.14
.
Your tests are still failing with this version. Compare changes