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

[greenkeeper]

The devDependency np was updated from 4.0.2 to 5.0.0.

🚨 View failing branch.

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

• ✅ ci/circleci: test: Your tests passed on CircleCI! (Details).
• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#26

---

Commits

The new version differs by 22 commits.

• 3727b22 5.0.0
• e7b9426 Update dependencies
• 3601af5 Fix multiple version bumps when publishing using Yarn (#389)
• fed7766 Fix release draft task
• ce7e550 Add --no-release-draft flag to skip opening a GitHub release draft page (#379)
• 45cea18 Fix version prompt and config (#385)
• 9dac7aa Support setting flags globally and locally using cosmiconfig (#354)
• c7d4cd0 Rollback Git operations when publish fails and on termination (#334)
• a02e169 Drop question Will bump from X to Y. Continue? (#377)
• 3c436cf Rename npm-util.js and improve method naming (#374)
• a880f84 Add tip for releasing an update to an old version (#370)
• 537aa8e Verify installed Yarn version is >=1.7.0 (#360)
• 70fd0c1 Add issue and PR templates (#353)
• e8a3a7d Fix name check for private registries (#356)
• 72ebf7d Add external registry support to authentication check (#365)

There are 22 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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