search

simonepri / ni

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

An in-range update of np is breaking the build 🚨 #16

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 3.0.0 of np was just published.

Branch Build failing 🚨
Dependency np
Current Version 2.20.1
Type devDependency

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

np is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/simonepri/ni/builds/384295518?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 15 commits.

  • fba0ddf 3.0.0
  • 9a040c0 Bump other dependencies
  • d63af9a Upgrade rxjs and listr
  • 334a18d Add ability to publish a subdirectory (#263)
  • 3f1c66e Exit with non-zero exit code on SIGINT (#262)
  • 24fa0cd Skip all prerequisite checks when using --no-publish
  • e4b85e1 Skip "Ping npm registry" task when using --no-publish (#226)
  • 35cf989 Bump any-observable to support rxjs@6 (#267)
  • 1479d15 Fix yarn version bump for private packages (#257)
  • 305bdc4 Require Node.js 6
  • 6a86102 Use terminal-link module
  • 370ef63 Add confirmation message when no previous commits are found - fixes #242 (#245)
  • d0499c6 Switch between npm & yarn for tests (#246)
  • 18a850f Fix typo (#247)
  • 7278d2e Show list of commits before prompt - fixes #238 (#241)

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.20.1 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 3.0.1 just got published.

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

Commits

The new version differs by 2 commits.

See the full diff

greenkeeper[bot] commented 6 years ago

Version 3.0.2 just got published.

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

Commits

The new version differs by 2 commits.

  • 3dc7069 3.0.2
  • f291eff Fix dynamic commit hash abbreviation length (#272)

See the full diff

greenkeeper[bot] commented 6 years ago

Version 3.0.3 just got published.

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

Commits

The new version differs by 2 commits.

  • 5773d1c 3.0.3
  • 32675a3 Don't fail if the test run script doesn't exist when using Yarn

See the full diff

greenkeeper[bot] commented 6 years ago

Version 3.0.4 just got published.

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

Commits

The new version differs by 2 commits ahead by 2, behind by 2.

  • 846017b 3.0.4
  • acbaece Don't fail if the test run script doesn't exist when using Yarn

See the full diff