Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

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

Open
greenkeeper bot opened this issue Dec 3, 2018 · 2 comments
Open

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

greenkeeper bot opened this issue Dec 3, 2018 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 3, 2018

The devDependency progress was updated from 2.0.1 to 2.0.2.

🚨 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 devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ci/circleci: lint: Your tests passed on CircleCI! (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

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
Contributor Author

greenkeeper bot commented Dec 3, 2018

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 5, 2018

  • The devDependency progress was updated from 2.0.2 to 2.0.3.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

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

No branches or pull requests

0 participants