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 🚨 #107

Open
greenkeeper bot opened this issue Aug 14, 2017 · 1 comment
Open

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

greenkeeper bot opened this issue Aug 14, 2017 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Aug 14, 2017

Version 2.6.0 of broccoli-asset-rev just got published.

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

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

As broccoli-asset-rev 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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 8 commits.

  • e5ee2bc 2.6.0
  • 5cfdfaa Merge pull request #121 from RevolutionDisplay/two-stage
  • 433ced7 revert non-glob string exclusions to a substring search + unit test
  • 684c5ee extend basic test to verify .json files are different from .js #118
  • a9484bf extensions must match at the end of a string #118
  • cd54cd8 update filter-tests to explicitly read files using null encoding
  • 3d7b727 avoid es6 methods (node 0.12 friendly)
  • c41494c split fingerprint + rewrite into two stages to address #118

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
Author

greenkeeper bot commented Aug 14, 2017

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