rangle
[email protected] breaks build 🚨
Hello lovely humans,
codelyzer just published its new version 2.1.0.
| State | Failing tests :rotating_light: |
|---|---|
| Dependency | codelyzer |
| New version | 2.1.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build went from success to failure.
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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
| ✨ Try the all new Greenkeeper GitHub Integration ✨ |
|---|
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.Screencast Try it today. Free for private repositories during beta. |
