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 progress is breaking the build 🚨 #292

Open
greenkeeper bot opened this issue Oct 17, 2018 · 3 comments
Open

An in-range update of progress is breaking the build 🚨 #292

greenkeeper bot opened this issue Oct 17, 2018 · 3 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 17, 2018

The dependency progress was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

progress 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/appveyor/branch: AppVeyor build succeeded (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 11 commits.

  • 4951391 2.0.1
  • 744fcbf Add myself to maintainers in package.json
  • e74b880 Merge pull request #173 from turbopope/master
  • 501e9d2 Set renderThrottle in synch example to 100 ms
  • b2533ad Don't render if last render was less than renderThrottle ms ago
  • 10c2233 Remove the render throttle logic
  • 09e8286 Add a synchronous example
  • 30d70d9 Merge pull request #141 from trenskow/master
  • 52173f0 Merge pull request #149 from larshp/master
  • f37469e run render if throttle is zero
  • 8f110fe Math.floor percent.

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
Copy link
Author

greenkeeper bot commented Oct 17, 2018

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 3, 2018

  • The dependency progress was updated from 2.0.1 to 2.0.2.

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Author

greenkeeper bot commented Dec 5, 2018

  • The dependency progress was updated from 2.0.2 to 2.0.3.

Your tests are still failing with this version. Compare changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants