Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of fs-extra is breaking the build 🚨 #104

Closed
greenkeeper bot opened this issue Dec 5, 2017 · 1 comment
Closed

An in-range update of fs-extra is breaking the build 🚨 #104

greenkeeper bot opened this issue Dec 5, 2017 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 5, 2017

Version 4.0.3 of fs-extra was just published.

Branch Build failing 🚨
Dependency fs-extra
Current Version 4.0.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

fs-extra 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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 10 commits.

  • bd3376b 4.0.3
  • f934357 Merge pull request #520 from arcanis/patch-1
  • d21da93 Fixes fs-extra on linux
  • a6e8cd6 Add issue template (#514)
  • 2599b67 Merge pull request #501 from jprichardson/rimraf-backports
  • ddb5cb4 Use octal notation for chmod values in rimraf.js
  • cc6d425 Merge pull request #500 from revelt/patch-1
  • d416fa7 typo fixed
  • 41a33c2 Merge pull request #497 from nico29/docs/copy-improvements
  • 4f01664 docs: update copy to show differences with cp

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 5, 2017

After pinning to 4.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant