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 🚨 #50

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

The dependency @webcomponents/webcomponentsjs was updated from 2.2.10 to 2.3.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 **errored**.

Commits

The new version differs by 2186 commits.

  • 27ef16d Publish
  • a287394 Bump the URL polyfill to v0.7.3, which is already released in this state with this version.
  • e1c9dbb [HTMLImports] Fix issue with style elements in svg (#203)
  • 75908d9 Merge pull request #141 from webcomponents/add-htmlimports
  • 1cf8e3b disable style-paths test in edge 15 because of wonky loading behavior
  • 00f956e Fix weird timing issues on Edge
  • 43cfbdc Handle empty custom-styles when sorting (#201)
  • ed00416 Workaround weird Edge issue with <style> and @import
  • bf54d7d readystate can just be interactive forever on chrome 41
  • 11d820e [HTMLImports] fix chrome 41 timing
  • 68b7bd9 [HTMLImports] fix compilation
  • 0454208 Merge branch 'master' into add-htmlimports
  • 2e57e52 Fix issue with custom-style ordering under Custom Property shim (#199)
  • 1801bf2 Merge pull request #200 from webcomponents/upgrade-travis
  • edb06c6 remove explicit xvfb-run

There are 250 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 4 years ago

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

greenkeeper[bot] commented 4 years ago

Your tests are still failing with this version. Compare changes