This version is covered by your current version range and after updating it in your project the build failed.
As yeoman-assert 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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/zguillez/generator-starling/builds/200656172)
Commits
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.2.3 of yeoman-assert just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As yeoman-assert 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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/zguillez/generator-starling/builds/200656172)Commits
The new version differs by 5 commits .
fa51fc52.2.37d2945bAdd eslint as dev dependency446ff2dRemove last dependency by es6-ing a line of code69639aereduce dependencies and code complexity (#20)41b7f28Update dependencies to enable Greenkeeper 🌴 (#22)See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: