This version is covered by your current version range and after updating it in your project the build failed.
As gulp-minify-html 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
- ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/summer-snowflake/account-book-pig/runs/build/583712b5d2db080100ef6d56)
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).
After pinning to 1.0.5 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 1.0.6 of gulp-minify-html just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As gulp-minify-html 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
- ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/summer-snowflake/account-book-pig/runs/build/583712b5d2db080100ef6d56)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: