search

publ1us-g / pocket-protest-data

Web services supporting https://twitter.com/pocketprotest
https://pocketprotest.org
MIT License
1 stars 0 forks source link

An in-range update of tzwhere is breaking the build 🚨 #26

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.0.1 of tzwhere was just published.

Branch Build failing 🚨
Dependency tzwhere
Current Version 1.0.0
Type dependency

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

tzwhere 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 - ❌ **wercker/build** Wercker pipeline executing [Details](https://app.wercker.com/publ1us-g/pocket-protest-data/runs/build/5a316ca29fe1e000012bdfd6) - ❌ **bitHound - Dependencies** 5 failing dependencies. [Details](https://www.bithound.io/github/publ1us-g/pocket-protest-data/5e5d71ccc501449badb3a1cd5f896bf8c01ddeab/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/publ1us-g/pocket-protest-data/5e5d71ccc501449badb3a1cd5f896bf8c01ddeab/files?status=passing)
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 6 years ago

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