search

canjs / can-util

Essential utilities used by lots of CanJS's projects.
https://canjs.com/doc/can-util.html
MIT License
10 stars 8 forks source link

An in-range update of can-param is breaking the build 🚨 #453

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency can-param was updated from 1.1.1 to 1.1.2.

🚨 View failing branch.

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

can-param 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-util/builds/537543311?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 9 commits ahead by 9, behind by 1.

  • d14986b 1.1.2
  • c4a40a1 Update version number
  • 6a2e9c3 Merge pull request #16 from canjs/landscaper/qunit2
  • 5c39965 Landscaper: QUnit2 upgrade
  • ed9d72c Merge pull request #14 from canjs/greenkeeper/initial
  • 62ffbdf chore(package): update dependencies
  • fdf6c5e Merge pull request #13 from canjs/landscaper/update-default-repos
  • d6eb81a Update README.md
  • e205e0e Update README generated by DoneJS

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