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

Question

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

greenkeeper opened this issue 5 years ago · 6 comments

The devDependency np was updated from `5.2.1` to `6.0.0`.

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 failed on CircleCI (Details).

Release Notes for v6.0.0

Breaking

Require Node.js 10 818ff4b

Enhancements

Show registry URL before publishing (#485) 6bf85df
Allow publishing if availability check fails (#490) ccdb8a5
Publish non-private subdirectories when root is private (#483) 607e5c1
Enforce matching engines on npm install (#481) b14dbc9

Fixes

Fix checking collaborators when publishing to external registry (#491) 4ad4146

Docs

Document support for GitHub Packages 91ba1ef

v5.2.1...v6.0.0

Commits

The new version differs by 8 commits.

a44f05d 6.0.0
6bf85df Show registry URL before publishing (#485)
ccdb8a5 Allow publishing if availability check fails (#490)
607e5c1 Publish non-private subdirectories when root is private (#483)
4ad4146 Fix checking collaborators when publishing to external registry (#491)
b14dbc9 Enforce matching engines on npm install (#481)
91ba1ef Document support for GitHub Packages
818ff4b Require Node.js 10

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 🌴

Answer 1 · 2020-02-07T07:17:30.000Z

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

Answer 2 · 2020-02-17T08:36:24.000Z

The devDependency np was updated from 6.0.0 to 6.1.0.

Your tests are still failing with this version. Compare changes

Release Notes for v6.1.0

Auto-submit 2FA (#493) d589d46
Escape HTML in release note commit messages (#500) 05bb791

v6.0.0...v6.1.0

Commits

The new version differs by 4 commits.

cd046ca 6.1.0
d589d46 Auto-submit 2FA (#493)
32d6b1c Add FAQ section to the readme (#498)
05bb791 Escape HTML in release note commit messages (#500)

See the full diff

Answer 3 · 2020-02-28T08:23:57.000Z

The devDependency np was updated from 6.1.0 to 6.2.0.

Your tests are still failing with this version. Compare changes

Release Notes for v6.2.0

Allow explicit private publish to prevent public publish prompt (#497) 08b52a2
Add preview mode (#399) 5f52e81

v6.1.0...v6.2.0

Commits

The new version differs by 3 commits.

5d1a00b 6.2.0
08b52a2 Allow explicit private publish to prevent public publish prompt (#497)
5f52e81 Add preview mode (#399)

See the full diff

Answer 4 · 2020-04-12T15:16:04.000Z

The devDependency np was updated from 6.2.0 to 6.2.1.

Your tests are still failing with this version. Compare changes

Release Notes for v6.2.1

Fix scoped repo prompt showing even if package has already been published (#524) 1cf7d78
Correctly detect if np is not run in a package (#512) b5a7dcf

v6.2.0...v6.2.1

Commits

The new version differs by 5 commits.

5415f77 6.2.1
1cf7d78 Fix scoped repo prompt showing even if package has already been published (#524)
b5a7dcf Correctly detect if np isn't run in a package (#512)
d9848db Add tests for the config (#495)
eab7bbd Fix spacing in readme examples (#510)