search

pelias / model

Pelias data models
6 stars 17 forks source link

An in-range update of proxyquire is breaking the build 🚨 #114

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency proxyquire was updated from 2.0.2 to 2.1.0.

🚨 View failing branch.

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

proxyquire 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](https://travis-ci.org/pelias/model/builds/485217528?utm_source=github_status&utm_medium=notification)). - ❌ **ci/circleci: Build Error:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/pelias/model/6?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
Commits

The new version differs by 2 commits.

  • 8864361 2.1.0
  • 698ee67 Resolve nonexistent modules via path.resolve with noCallThru() (#216)

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

orangejulius commented 5 years ago

Looks like a false alarm. CircleCI was inadvertently set up for this repo when it's not needed.