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 putasset is breaking the build 🚨 #5

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

An in-range update of putasset is breaking the build 🚨 #5

greenkeeper bot opened this issue Dec 5, 2016 · 1 comment
Assignees

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 5, 2016

Version 1.0.9 of putasset just got published.

Branch Build failing 🚨
Dependency putasset
Current Version 1.0.8
Type dependency

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

As putasset is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes putasset v1.0.9

feature

  • (package) github v7.0.0
  • (package) nyc v10.0.0
Commits

The new version differs by 3 commits .

  • dac9a88 chore(package) v1.0.9
  • efc7803 feature(package) github v7.0.0
  • 07a9431 feature(package) nyc v10.0.0

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
Copy link
Contributor Author

greenkeeper bot commented Dec 5, 2016

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

@davelandry davelandry self-assigned this Dec 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant