An in-range update of codelyzer is breaking the build 🚨

[greenkeeper[bot]]

Version 2.0.0 of codelyzer just got published.

Branch	Build failing 🚨
Dependency	codelyzer
Current Version	2.0.0-beta.4
Type	devDependency

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

As codelyzer 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 is in progress [Details](https://travis-ci.org/sethbergman/ng2-admin/builds/199422498) - ❌ **continuous-integration/codeship** Build failed [Details](https://app.codeship.com/projects/200379/builds/22412739)

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:

[greenkeeper[bot]]

Version 2.0.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

2.0.1

Features

• Improve testing #235 77ef89e
• Log template parsing errors on log-level debug #227 19fdabf
• Better error messages for template-use-public #229 0b7e459
• Support for Angular 4.0.0-beta.8 #241 98639a9

Bug Fixes

• Fix semantic error when declaration's generation is enabled #221 c694405
• Inconsistent links to the style guide sections #233 c9e87f6