jhwohlgemuth/applied

An in-range update of fs-promise is breaking the build 🚨

greenkeeper opened this issue · 1 comments

greenkeeper commented

Version 2.0.1 of fs-promise just got published.

Branch Build failing 🚨
Dependency fs-promise
Current Version 2.0.0
Type devDependency

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

As fs-promise is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

  • ✅ coverage/coveralls First build on greenkeeper/fs-promise-2.0.1 at 100.0% Details

  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

  • ✅ bitHound - Dependencies No failing dependencies. Details

  • ❌ bitHound - Code 7 failing files. Details

Commits

The new version differs by 3 commits .

  • 3f53728 Version 2.0.1
  • 75fe5a5 Merge pull request #22 from SBD580/master
  • 90fd3d4 Move Types dependencies to devDependencies

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

greenkeeper commented

Version 2.0.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits .

  • 7bc0779 Version 2.0.2
  • c37c1e1 Merge pull request #25 from kevinbeaty/mz/fs
  • 88c9a34 Update list of mz/fs functions to proxy, add test for mkdtemp()

See the full diff.