An in-range update of can-fixture is breaking the build 🚨

greenkeeper[bot] commented 5 years ago

The devDependency can-fixture was updated from `3.0.5` to `3.1.0`.

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

can-fixture 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 could not complete due to an error ([Details](https://travis-ci.org/canjs/can-connect/builds/524243386?utm_source=github_status&utm_medium=notification)).

Release Notes for support Promise and Async/Await

This release adds support for the requestHandler to return promises. #164

Commits

The new version differs by 9 commits.

70675d2 3.1.0
fb0e597 support returning promises from dynamic fixtures (#164)
1559de9 Merge pull request #161 from canjs/greenkeeper/testee-0.9.0
dc35384 Fix the description in the README
8832773 Update Slack link
de2ee48 Merge pull request #162 from canjs/landscaper/update-default-repos
5f20010 Update README.md
af75388 Update README generated by DoneJS
5a9d5da chore(package): update testee to version 0.9.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 3.0.5 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago