An in-range update of core-js is breaking the build 🚨

Question

An in-range update of core-js is breaking the build 🚨

greenkeeper opened this issue 7 years ago · comments

Version 2.5.2 of core-js was just published.

Branch	Build failing 🚨
Dependency	core-js
Current Version	2.5.1
Type	dependency

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

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

2.5.2 - 2017.12.09

MutationObserver no longer used for microtask implementation in iOS Safari because of bug with scrolling, #339
Fixed JSON.stringify(undefined, replacer) case in the wrapper from the Symbol polyfill, #345
Array() calls changed to new Array() for V8 optimisation

Commits

The new version differs by 24 commits.

a03fd19 2.5.2
1dfbedd revert Symbol.asyncIterator - leave changes like this for core-js@3
f2fc21a update eslint and webpack
23904b8 fix #339
adeb69d fix #345
5c0fe50 update grunt-contrib-uglify
7f43485 update eslint
16c775f update eslint
0e05248 Merge pull request #350 from rqrqrqrq/feature/spelling
616b90c fix typos in readme
df3e18c update eslint
83ef517 move async iteration to the stage 3
ab8ad81 update some dev dependencies
e44fc05 sort the list of dev dependencies, use caret ranges for some of dev dependencies
bca7744 update eslint

There are 24 commits in total.

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 · Answer 1 · Sat Dec 09 2017 20:37:53 GMT+0800 (China Standard Time)

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

greenkeeper · Answer 2 · Tue Dec 12 2017 04:50:38 GMT+0800 (China Standard Time)

Version 2.5.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

2.5.3 - 2017.12.12

Fixed calling onunhandledrejectionhandler multiple times for one Promise chain, #318
Forced replacement of String#{padStart, padEnd} in Safari 10 because of a bug, #280
Fixed Array#@@iterator in a very rare version of WebKit, #236 and #237
One more #345-related fix

Commits

The new version differs by 9 commits ahead by 9, behind by 2.

f96b8d8 2.5.3
05f2525 2.5.2
e5e61c7 revert Symbol.asyncIterator - leave changes like this for core-js@3
cd78e42 validate replacer argument of JSON.stringify, #345
2b314f8 fix #280
4024915 fix #318
e1ffbae fix #236, #237
fc1134c update builder dependencies
1b0455c update changelog

See the full diff

greenkeeper · Answer 3 · Sat May 26 2018 19:51:47 GMT+0800 (China Standard Time)

Version 2.5.7 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

2.5.7 - 2018.05.26

Get rid of reserved variable name final, related #400

Commits

The new version differs by 44 commits ahead by 44, behind by 3.

5bbe230 2.5.7
accc97e 2.5.6
26834c2 add modern version internal debugging information about used versions
78dd32c add a webos-related comment
503528f fix v8 6.6 (Node 10 and Chrome 66) Promise bug with resolving custom thenables
f98d2f5 fix #396
aa7feac 2.5.5
cf04ba3 fix #392, #393
5d0e936 2.5.4
916ba13 fix one case of built-in iterators deoptimization in V8, related #377
db8f257 revert e1ffbae because of #368
ab605b2 2.5.3
ea9f44d 2.5.2
5b47e1d revert Symbol.asyncIterator - leave changes like this for core-js@3
de5ed6f update changelog

There are 44 commits in total.

See the full diff