search

PalatinCoder / Dorfolympiade

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

An in-range update of @polymer/polymer is breaking the build 🚨 #3

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency @polymer/polymer was updated from 3.0.5 to 3.1.0.

🚨 View failing branch.

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

@polymer/polymer 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 101 commits.

  • 2d9d602 3.1.0
  • 99e3970 update dependencies
  • 8510c66 Merge pull request #5412 from Polymer/before-register-externs
  • 0492390 Add beforeRegister callback to externs
  • 693f9e4 Make toggleAttribute match with native signature (#5372)
  • 750e7e1 Fixed typos on lines 133 and 157 (#5409)
  • ce85eb9 Fix signature of toggleAttribute to match native version (#5370)
  • 96557f7 Update jsdoc for PropertyEffects.splice (#5367)
  • 9b322c2 Merge pull request #5361 from Polymer/listen-node-type
  • b55c56f Expand type of LegacyElementMixin#listen and unlisten to accept EventTargets.
  • 9dbc872 Update gen-closure-declarations to 0.5.0 (#5360)
  • 912c19c Add TypeScript types for observer parameters. (#5359)
  • 4f11628 Merge pull request #5357 from a-xin/improve-legacy-typings
  • 239e99a Add missing return type to attributeChanged
  • bf02bd3 Add specific type for behaviors

There are 101 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 3.0.5 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.