search

PalatinCoder / Dorfolympiade

BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

An in-range update of @webcomponents/webcomponentsjs is breaking the build 🚨 #7

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency @webcomponents/webcomponentsjs was updated from 2.1.3 to 2.2.0.

🚨 View failing branch.

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

@webcomponents/webcomponentsjs 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 - ❌ **Travis CI - Branch:** The build **failed**.
Commits

The new version differs by 16 commits.

  • 81beb06 2.2.0
  • 9f650d0 update dependencies
  • 8f75815 Merge pull request #1049 from webcomponents/1047-kschaaf-toString-fix
  • 215f82e Just test null/undefined; window comes up differently on old browsers.
  • 099497a Add tests for Symbol toString patch
  • 7f939d9 Update to latest wct.
  • 2e0a9d7 Patch toString implementation to be correct and strict-mode compatible.
  • 9bcea90 docs(readme): use semver range for CDN URL (#1045)
  • 87031ad Merge pull request #1032 from webcomponents/v2-keep-fn-name
  • 1b7db38 Merge pull request #1043 from webcomponents/externs-2
  • 8e37e57 externs annotation must come first
  • f3983f5 Merge pull request #1033 from webcomponents/force-modules-v2
  • 0990782 Force Closure to see files as modules by exporting {}
  • e1265ce Set keepFnName in custom-elements-es5-adapter babel config
  • 08d77e2 Update Promise polyfill link [skip ci] (#1018)

There are 16 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 5 years ago

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