search

chaitanyapotti / Vault-Sc

Vault Smart Contracts
MIT License
3 stars 2 forks source link

An in-range update of electusaction is breaking the build 🚨 #30

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency electusaction was updated from 2.5.1 to 2.5.2.

🚨 View failing branch.

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

electusaction 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 - ❌ **ci/circleci: test-coverage:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/chaitanyapotti/Vault-Sc/245?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
Commits

The new version differs by 12 commits.

  • b9d719e Updated packages and ci
  • 8ecc665 Updated packages and ci
  • 6ab7a92 Merge pull request #19 from chaitanyapotti/greenkeeper/eslint-config-prettier-6.0.0
  • cb2f31c chore(package): update lockfile package-lock.json
  • cee9746 chore(package): update eslint-config-prettier to version 6.0.0
  • 3883824 Merge pull request #17 from chaitanyapotti/greenkeeper/eslint-config-prettier-5.0.0
  • 4260f4c Merge branch 'master' into greenkeeper/eslint-config-prettier-5.0.0
  • e7931ab Merge pull request #18 from chaitanyapotti/greenkeeper/eslint-6.0.0
  • f2c9dab chore(package): update lockfile package-lock.json
  • bd9c48d chore(package): update eslint to version 6.0.0
  • e27923c chore(package): update lockfile package-lock.json
  • f1777a3 chore(package): update eslint-config-prettier to version 5.0.0

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

chaitanyapotti commented 5 years ago

Fixed