search

manGoweb / mango-cli

A project scaffolding and build tool to accelerate your development
http://mangocli.org
MIT License
30 stars 9 forks source link

An in-range update of node-notifier is breaking the build 🚨 #306

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 5 years ago

The dependency node-notifier was updated from 5.4.2 to 5.4.3.

🚨 View failing branch.

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

node-notifier 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 is in progress ([Details](https://travis-ci.org/manGoweb/mango-cli/builds/573774241?utm_source=github_status&utm_medium=notification)). - ✅ **ci/circleci:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/manGoweb/mango-cli/870?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/Onset/mango-cli/builds/26793969)).
Commits

The new version differs by 8 commits.

  • 1101e6d Update version to v5.4.3
  • d204329 Revert "Fixes tests after mapping change"
  • 9a1fc72 Update lock file after audit
  • 8769921 Revert "Bumps all dependencies"
  • 3ae8fd7 Merge pull request #284 from mikaelbr/revert-271-overwritable-timeout
  • 5c48dc8 Revert "Allow timeout: false to remove a timeout"
  • 722f9d9 Revert "Remove node 6 from travis run"
  • 12d971d Revert "v5.4.2"

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