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 broccoli-asset-rev is breaking the build 🚨 #109

Open
greenkeeper bot opened this issue Mar 29, 2018 · 1 comment
Open

An in-range update of broccoli-asset-rev is breaking the build 🚨 #109

greenkeeper bot opened this issue Mar 29, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Mar 29, 2018

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.7.0 of broccoli-asset-rev was just published.

Branch Build failing 🚨
Dependency broccoli-asset-rev
Current Version 2.6.0
Type devDependency

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

broccoli-asset-rev is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • 087417f 2.7.0
  • 81de916 Merge pull request #125 from ef4/fastboot-manifest-with-tests
  • 631c552 dropping ancient node from ci
  • 4e9aea2 Maintain correctness when rewriting fastboot-capable apps
  • 1ad8086 Merge pull request #123 from rickharrison/broccoli-asset-rev/patch-1
  • 772d90f README: Slightly more careful markdown

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 Mar 29, 2018

After pinning to 2.6.0 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