-
Notifications
You must be signed in to change notification settings - Fork 70
An in-range update of core-js is breaking the build 🚨 #40
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
Comments
After pinning to 2.5.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 2.5.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits ahead by 10, behind by 6.
See the full diff |
Version 2.5.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 17 commits ahead by 17, behind by 8.
There are 17 commits in total. See the full diff |
Version 2.5.7 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes2.5.7 - 2018.05.26
CommitsThe new version differs by 19 commits ahead by 19, behind by 13.
There are 19 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for 2.6.0 - 2018.12.05CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes Release Notes for 2.6.4 - 2019.02.07
CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for 2.6.5 - 2019.02.15
|
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.5.4 of core-js was just published.
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
2.5.4 - 2018.03.27Promise
, #367Number.{parseInt, parseFloat}
entry points__(define|lookup)[GS]etter__
export in thelibrary
versionCommits
The new version differs by 25 commits ahead by 25, behind by 3.
f1e504b
2.5.4
795c6bd
fix one case of built-in iterators deoptimization in V8, related #377
22ebb62
revert e1ffbae because of #368
fdd01be
2.5.3
439eb51
2.5.2
ab1120b
revert
Symbol.asyncIterator
- leave changes like this forcore-js@3
e3b91cd
update changelog
658d918
update
qunit
00ec51a
update
eslint
0dc45b6
update
karma-qunit
,qunitjs
->qunit
1bb028f
update
eslint-plugin-import
064707e
Merge pull request #382 from nicolasleger/patch-1
c8c982d
[CI] Update node versions
678ff64
update dependencies
6e5bf6f
update
eslint
There are 25 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 🌴
The text was updated successfully, but these errors were encountered: