search

satya164 / quik

:rocket: A quick way to prototype and build apps with React and Babel with zero-setup.
526 stars 30 forks source link

An in-range update of eslint-plugin-babel is breaking the build 🚨 #315

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 4.1.2 of eslint-plugin-babel just got published.

Branch Build failing 🚨
Dependency eslint-plugin-babel
Current Version 4.1.1
Type devDependency

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

As eslint-plugin-babel 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 - ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/260266) - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/satya164/quik/builds/257473744?utm_source=github_status&utm_medium=notification)
Release Notes v4.1.2

Bug Fix

babel/semi: doesn't fail when using for await (let something of {}). Includes class properties

Commits

The new version differs by 2 commits.

  • 1eab147 4.1.2
  • 9468524 Modifying semi rule to support for await (#126)

See the full diff

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] commented 7 years ago

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