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

[greenkeeper]

The dependency object.values was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

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

object.values 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 failed (Details).

---

Commits

The new version differs by 11 commits.

• e00dd4a v1.1.1
• a8ac36f [Refactor] use split-up es-abstract (85% bundle size decrease)
• e8a9297 [actions] add automatic rebasing / merge commit blocking
• 110dbca [meta] add funding field
• c74ad8a [Dev Deps] update eslint, @ljharb/eslint-config, functions-have-names
• 80080cd [Tests] use npx aud instead of nsp or npm audit with hoops
• 2a82dea [Tests] use shared travis-ci configs
• 58a4209 [Tests] up to node v12.7, v11.15, v10.16, v8.16, v6.17; use nvm install-latest-npm
• 9b7c99b [Deps] update es-abstract
• 10adf18 [Dev Deps] update object-keys, tape, eslint
• 40746e5 [Tests] use functions-have-names

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.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.