-
Notifications
You must be signed in to change notification settings - Fork 6
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 core-js is breaking the build 🚨 #65
Comments
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. |
Your tests are still failing with this version. Compare changes Release Notes for 3.2.1 - 2019.08.12
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.0 - 2019.10.13
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.1 - 2019.10.13
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.2 - 2019.10.14
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.3 - 2019.10.22
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.4 - 2019.10.25
|
Your tests are still failing with this version. Compare changes Release Notes for 3.3.5 - 2019.10.29
|
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes Release Notes for 3.4.0 - 2019.11.07
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.1 - 2019.11.12
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.2 - 2019.11.22
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.3 - 2019.11.26
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.4 - 2019.11.27
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.5 - 2019.11.28
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.6 - 2019.12.03
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.7 - 2019.12.03
|
Your tests are still failing with this version. Compare changes Release Notes for 3.4.8 - 2019.12.09
|
Your tests are still failing with this version. Compare changes Release Notes for 3.5.0 - 2019.12.12
|
Your tests are still failing with this version. Compare changes Release Notes for 3.6.0 - 2019.12.19
|
Your tests are still failing with this version. Compare changes Release Notes for 3.6.1 - 2019.12.25
|
The dependency 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 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
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. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: