canjs / can-connect

Model layer utilities for every JavaScript framework! Assemble real-time, high performance, restful data connections.
https://canjs.com/doc/can-connect.html
MIT License
29 stars 16 forks source link

An in-range update of can-make-rest is breaking the build 🚨 #493

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

The dependency can-make-rest was updated from 0.1.3 to 0.1.4.

🚨 View failing branch.

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

can-make-rest 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 - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/canjs/can-connect/builds/575039137?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 13 commits.

  • 477d173 Update version number
  • 19a312c Landscaper: QUnit2 upgrade
  • 0f63541 Merge pull request #27 from canjs/landscaper/travis-xenial
  • fa87300 Migrate to xenial in travis
  • 265f0d4 Merge pull request #22 from canjs/greenkeeper/initial
  • 2e07f11 docs(readme): add Greenkeeper badge
  • 2ce7686 chore(package): update dependencies
  • 781e336 Merge pull request #20 from canjs/landscaper/4217-use-strict
  • 793f63f Adds use strict. Fixes canjs/canjs#4217
  • 207a148 Merge pull request #19 from canjs/can-util-removal
  • 35c37e9 use canReflect.eachKey instead of canReflect.each
  • 3b0e26a fix can-reflect version
  • 30c2daf get rid of can-util

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 4 years ago

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