search

EndyKaufman / kaufman-bot

Simple bot for telegram
https://telegram.me/KaufmanBot
26 stars 8 forks source link

An in-range update of forever-monitor is breaking the build 🚨 #63

Closed greenkeeper[bot] closed 3 years ago

greenkeeper[bot] commented 4 years ago

The dependency forever-monitor was updated from 1.7.1 to 1.7.2.

🚨 View failing branch.

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

forever-monitor 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/EndyKaufman/kaufman-bot/builds/632833632?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 18 commits.

  • 351aaa5 [dist] Version bump. 1.7.2
  • c272863 [fix test] Remove spurrious test assertion.
  • 6bf80a9 Move from travis to circleci (#171)
  • a396a52 Merge pull request #173 from foreverjs/chore/172-update-utile
  • 6dfc0e6 Update utile. Update chokidar
  • 1aa2ccb Merge pull request #157 from bennyn/patch-1
  • 980ccf6 Merge pull request #116 from ThomasR/patch-1
  • 17dc8b5 Merge pull request #136 from alex7071/master
  • bedc17b Remove package-lock
  • ece7759 Merge pull request #170 from foreverjs/chore/git-ignores
  • 35dbaec Update ignores
  • c1d96ca Merge pull request #169 from foreverjs/chore/update-travis
  • def69a5 Update Travis configuration
  • 56f7475 Added watch multi test and updated README.md
  • 43e4c54 [fix doc] Typo in 'watch:restart'

There are 18 commits in total.

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