Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Dec 12, 2019 · 2 comments
Open

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

greenkeeper bot opened this issue Dec 12, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 12, 2019

The dependency object.entries 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.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 is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 11 commits.

  • 22eb832 v1.1.1
  • 3fd42b9 [Refactor] use split-up es-abstract (85% bundle size decrease)
  • bf480ef [Dev Deps] update eslint, @ljharb/eslint-config, functions-have-names
  • 576c8a7 [Tests] use shared travis-ci configs
  • 3253bdf [actions] add automatic rebasing / merge commit blocking
  • 26c5a45 [Tests] up to node v12.7, v11.15, v10.16, v8.16, v6.17; use nvm install-latest-npm
  • 8cd5de5 [Tests] use functions-have-names
  • 3a2ca03 [Deps] update es-abstract
  • 908f4fd [meta] clean up scripts
  • 9bf7f7f [Tests] use npx aud instead of nsp or npm audit with hoops
  • 213436c [Dev Deps] update eslint, tape

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
Copy link
Contributor Author

greenkeeper bot commented Dec 12, 2019

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.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 20, 2020

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 10 commits.

  • 9470975 v1.1.2
  • 29e2771 [meta] add auto-changelog
  • 5552db4 [Dev Deps] update @ljharb/eslint-config, aud
  • db94733 [Refactor] use callBound instead of function-bind
  • fffb674 [Fix] do not mutate the native function when present
  • 124d3bb [Dev Deps] update eslint, @ljharb/eslint-config, tape; add aud
  • bcf93d0 [Deps] update es-abstract
  • 13c35c9 [meta] only run aud on prod deps
  • f30dde0 [Dev Deps] update eslint, @ljharb/eslint-config, tape, functions-have-names; add safe-publish-latest
  • 9374fed [Deps] update es-abstract

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants