tsg-ut / mnemo

TSGが制作しているプログラミング風パズルゲーム
https://mnemo.pro/
MIT License
26 stars 4 forks source link

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

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.5.6 of core-js was just published.

Branch Build failing 🚨
Dependency core-js
Current Version 2.5.5
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 could not complete due to an error [Details](https://travis-ci.org/tsg-ut/mnemo/builds/375907903?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 17 commits ahead by 17, behind by 8.

  • c31ae34 2.5.6
  • 3bbe23d add modern version internal debugging information about used versions
  • cfd9371 add a webos-related comment
  • 1e8a890 fix v8 6.6 (Node 10 and Chrome 66) Promise bug with resolving custom thenables
  • 3520378 fix #396
  • 7902263 2.5.5
  • 8a6e82a fix #392, #393
  • b34b0c3 2.5.4
  • 3119c26 fix one case of built-in iterators deoptimization in V8, related #377
  • c77b93a revert e1ffbae because of #368
  • 902d4f8 2.5.3
  • 86d7a90 2.5.2
  • c4c2843 revert Symbol.asyncIterator - leave changes like this for core-js@3
  • 167408c update changelog
  • 9f7fcc1 disable Node 10 on Travis on master and v2 branches because of some strange livescript-related issues (reproducible only on Travis), will be restored on v3 branch

There are 17 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] commented 6 years ago

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