search

noflo / noflo-react

Facebook React components for NoFlo
MIT License
20 stars 4 forks source link

An in-range update of es6-shim is breaking the build 🚨 #58

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency es6-shim was updated from 0.35.4 to 0.35.5.

🚨 View failing branch.

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

es6-shim 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/appveyor/branch:** Waiting for AppVeyor build to complete ([Details](https://ci.appveyor.com/project/bergie/noflo-react/builds/22919759)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/noflo/noflo-react/builds/503466457?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 5 commits.

  • d5e8698 v0.35.5
  • 73269b1 [Tests] up to node v11.11, v10.15, v8.15, v6.17
  • 003ee5d [Fix] es6-sham: Function.prototype.name: don’t poison the getter when the receiver is Function.prototype
  • e8a828d [Dev Deps] update eslint, @ljharb/eslint-config
  • 8ac5c6d [Dev Deps] remove jscs and jshint

See the full diff

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 5 years ago

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