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

[greenkeeper[bot]]

Version 2.5.7 of core-js was just published.

Branch	Build failing 🚨
Dependency	core-js
Current Version	2.5.6
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 is in progress [Details](https://travis-ci.org/levgaas/angular-tuned/builds/384064301?utm_source=github_status&utm_medium=notification) - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/levgaas/angular-tuned/187?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

---

Release Notes

2.5.7 - 2018.05.26

• Get rid of reserved variable name final, related #400

Commits

The new version differs by 19 commits ahead by 19, behind by 13.

• 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 19 commits in total.

See the full diff

FAQ 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:

[greenkeeper[bot]]

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