unional / jspm-config

Read information from jspm config and such
MIT License
1 stars 0 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.5.0 of core-js just got published.

Branch Build failing 🚨
Dependency core-js
Current Version 2.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As core-js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/unional/jspm-config/builds/261541866?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 99 commits.

  • 63ae52d 2.5.0
  • 998f32e update eslint
  • 9025b48 add .of and .from methods on collection constructors to readme
  • 20f055b add Array#flatten and Array#flatMap to readme
  • 860efb6 fix a typo
  • b9203ee update list of iterable DOM collections in readme
  • b4c2e5e remove some unused variables, update changelog
  • fc32be8 add Promise#try to readme
  • ea82fd9 remove caching Function#name, fix #296
  • fd850c3 add Promise#finally to readme
  • a41dd09 fix IE11 WeakMap frozen keys after zloirock/core-js@a69f577
  • 09f45b6 remove tests of excess DOM collections methods - FF have it, I don't think that removing those methods in core-js make sense
  • d230280 fix the list of whitespaces in the Number constructor test
  • 7c39430 move Array#flatten and Array#flatMap to stage 1 per July TC39 meeting
  • d35736f move Promise#finally to stage 3 per July TC39 meeting

There are 99 commits in total.

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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

greenkeeper[bot] commented 7 years ago

Version 2.5.1 just got published.

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

Release Notes 2.5.1 - 2017.09.01
  • Updated Promise#finally per tc39/proposal-promise-finally#37
  • Optimized usage of some internal helpers for reducing size of shim version
  • Fixed some entry points for virtual methods
Commits

The new version differs by 11 commits.

See the full diff