Closed greenkeeper[bot] closed 5 years ago
After pinning to 3.1.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
core-js was updated from 3.2.0
to 3.2.1
.Your tests are still failing with this version. Compare changes
Promise
polyfills, #615
The devDependency core-js was updated from
3.1.4
to3.2.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
core-js 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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Chimeejs/chimee/builds/569713734?utm_source=github_status&utm_medium=notification)).Release Notes for 3.2.0 - 2019.08.09
Promise.allSettled
moved to stable ES, per July TC39 meetingPromise.any
moved to stage 2,.errors
property ofAggregateError
instances maked non-enumerable, per July TC39 meetingusing
statement proposal moved to stage 2, addedSymbol.asyncDispose
, per July TC39 meetingArray.isTemplateObject
stage 2 proposal, per June TC39 meetingMap#updateOrInsert
stage 1 proposal, per July TC39 meetingMath.hypot
V8 7.7 bug, since it's still not stable without adding results tocore-js-compat
Promise
, #579 - added.finally
and patched.then
to / on nativePromise
prototype{ Map, Set, WeakMap, WeakSet }.deleteAll
DISABLE_OPENCOLLECTIVE
env variable topostinstall
scriptcore-js-pure
dependency fromcore-js-compat
, #590core-js-compat
on Windows, #606FAQ 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: