search

simonepri / ni

📦 A better `npm init` **NOT RELEASED**
MIT License
12 stars 0 forks source link

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

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.4.0 of update-notifier was just published.

Branch Build failing 🚨
Dependency update-notifier
Current Version 2.3.0
Type dependency

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

update-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 failed [Details](https://travis-ci.org/simonepri/ni/builds/358100066?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 6 commits.

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

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

greenkeeper[bot] commented 6 years ago

Version 2.5.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v2.5.0

Add ability to bypass isNpm check with shouldNotifyInNpmScript option.

Commits

The new version differs by 2 commits.

  • 5cd6577 2.5.0
  • ac0d3cb Add ability to bypass isNpm check with shouldNotifyInNpmScript option (#127)

See the full diff