Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of konva is breaking the build 🚨 #603

Closed
greenkeeper bot opened this issue Nov 8, 2018 · 2 comments
Closed

An in-range update of konva is breaking the build 🚨 #603

greenkeeper bot opened this issue Nov 8, 2018 · 2 comments
Labels
dependencies Pull requests that update a dependency file
Milestone

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Nov 8, 2018

The dependency konva was updated from 2.5.0 to 2.5.1.

🚨 View failing branch.

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

konva 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 failed (Details).

Commits

The new version differs by 6 commits.

  • d488686 update cdn link
  • 2d0cfdd build for 2.5.1
  • 8327371 update CHANGELOG with new version
  • b085ece Use custom functions for trimRight and trimLeft (for better browsers support)
  • 16caf0a Merge pull request #480 from IgorBabkin/443-get-children-generics
  • 3a3d094 Methods which return Konva.Collection have problems with generic typing #443

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper greenkeeper bot added the dependencies Pull requests that update a dependency file label Nov 8, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 8, 2018

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

@ivmartel ivmartel added this to the 0.26.0 milestone Dec 12, 2018
@ivmartel
Copy link
Owner

ivmartel commented Dec 13, 2018

(the tests were failing because of a Node update)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

1 participant