search

brunobesson / c2c-stats

https://brunobesson.github.io/c2c-stats/
GNU Affero General Public License v3.0
0 stars 0 forks source link

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

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 4.1.0 of codelyzer was just published.

Branch Build failing 🚨
Dependency codelyzer
Current Version 4.0.2
Type devDependency

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

codelyzer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/brunobesson/c2c-stats/builds/330506773?utm_source=github_status&utm_medium=notification)
Release Notes 4.1.0

Features

  • Feature request: no output named after a standard DOM event #473 ae3f07b
  • Support for Angular Compiler 5.2 #496 6a6b3de

Bug Fixes

  • i18n check-text edge cases #442 4c1c8d4
  • Codelyzer hanging for "styles" attribute in Angular component #446 a31c6d2 and 9c90ac3
  • no-output-on-prefix incorrectly throws error if output property name starts with "one" #480 9b844cc

Thanks to @gbilodeau for NoOutputNamedAfterStandardEventRule and wKoza for the code reviews!

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

After pinning to 4.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.