This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-angular 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/codeship** Build in progress [Details](https://app.codeship.com/projects/144819/builds/23155898)
- ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/rohan-buchner/MHWDashboard_Alpha/runs/build/58bc5e2d5df0e10100d97bce)
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 1.6.2 of eslint-plugin-angular just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-angular 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/codeship** Build in progress [Details](https://app.codeship.com/projects/144819/builds/23155898) - ❌ **wercker/build** Wercker pipeline failed [Details](https://app.wercker.com/rohan-buchner/MHWDashboard_Alpha/runs/build/58bc5e2d5df0e10100d97bce)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: