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 sol-merger is breaking the build 🚨 #876

Open
greenkeeper bot opened this issue Jan 7, 2020 · 2 comments
Open

An in-range update of sol-merger is breaking the build 🚨 #876

greenkeeper bot opened this issue Jan 7, 2020 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jan 7, 2020

The devDependency sol-merger was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

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

sol-merger 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
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
  • ci/circleci: clash-check: CircleCI is running your tests (Details).
  • ci/circleci: st-storage-layout-check: CircleCI is running your tests (Details).
  • ci/circleci: coverage: Your tests failed on CircleCI (Details).

Commits

The new version differs by 1 commits.

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

greenkeeper bot commented Jan 7, 2020

After pinning to 1.2.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
Contributor Author

greenkeeper bot commented Jan 7, 2020

  • The devDependency sol-merger was updated from 1.1.1 to 1.2.2.

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

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