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 require-plus is breaking the build 🚨 #22

Open
greenkeeper bot opened this issue Apr 28, 2018 · 2 comments
Open

An in-range update of require-plus is breaking the build 🚨 #22

greenkeeper bot opened this issue Apr 28, 2018 · 2 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Apr 28, 2018

Version 2.2.0 of require-plus was just published.

Branch Build failing 🚨
Dependency require-plus
Current Version 2.1.2
Type dependency

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

require-plus 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
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 1 commits.

  • dd4a971 v2.2.0 - bumped deps and added appveyor

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
Author

greenkeeper bot commented Apr 28, 2018

Version 2.2.1 just got published.

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

Commits

The new version differs by 1 commits.

  • c63ccf4 v2.2.1 - fixed node versions for travis

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Apr 28, 2018

After pinning to 2.1.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

0 participants