An in-range update of nopt is breaking the build 🚨

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency nopt was updated from `4.0.1` to `4.0.2`.

🚨 View failing branch.

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

nopt 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/semantic-release/cli/builds/659916426?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 8 commits.

53f158e 4.0.2
ab3c030 gh actions and such
0cc49ae better gitignore
936b2ae update tap
ee16dde auto-publish scripts
51b5db2 Allow empty array value if type def includes Array
fe0f6e5 chore: update CI for current Node LTS
8f6940f deps: bump tap

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

The dependency nopt was updated from 4.0.2 to 4.0.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

2b1ef35 4.0.3
c7db20d make package smaller

See the full diff

greenkeeper[bot] commented 4 years ago

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

semantic-release / cli