An in-range update of object.entries is breaking the build 🚨

[greenkeeper]

The dependency object.entries was updated from 1.0.4 to 1.1.0.

🚨 View failing branch.

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

object.entries is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 12 commits.

• e19be64 v1.1.0
• 89415ba [Tests] up to node v11.6, v10.15, v8.15, v6.16
• 074677d [Dev Deps] update eslint, @ljharb/eslint-config, covert, tape
• bc3e6a7 [Tests] use npm audit instead of nsp
• 052aed1 [Tests] remove jscs
• 0015678 [Tests] up to node v11.1, v10.13, v9.11, v8.12, v7.10, v6.14, v4.9; use nvm install-latest-npm
• 91f9ee6 [Dev Deps] update eslint, @ljharb/eslint-config, nsp, tape
• 9799c0d [New] add auto entry point`
• db5d97e [Deps] update define-properties, es-abstract, function-bind, has
• d192ab7 Only apps should have lockfiles
• 6f19e66 [Tests] up to node v7.4, v4.7; improve test matrix
• 3ae9c91 Exclude test.html from the npm package.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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