Upgrade np: 5.1.2 → 6.0.0 (major)

[depfu[bot]]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ np (5.1.2 → 6.0.0) · Repo

Release Notes

6.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

5.2.1

• Don't check "files" in package.json or .npmignore if private package or not publishing (#472) 000ddcf
• Don't ask for tag if --no-publish (#473) 23524b5
• Check package name availability in custom registry (#429) 8360cb6
• Fix incorrectly showing "Aborted!" message on successful publish (#471) e53cbe8

v5.1.3...v5.2.1

5.1.3

• Fix global detection for when Node.js was installed with Homebrew 1b28020

v5.1.2...v5.1.3

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 18 commits:

• 6.0.0
• Show registry URL before publishing (#485)
• Allow publishing if availability check fails (#490)
• Publish non-private subdirectories when root is private (#483)
• Fix checking collaborators when publishing to external registry (#491)
• Enforce matching engines on npm install (#481)
• Document support for GitHub Packages
• Require Node.js 10
• 5.2.1
• Fix double-encoding of the release notes
• 5.2.0
• Update dependencies
• Don't check `"files"` in package.json or `.npmignore` if private package or not publishing (#472)
• Don't ask for tag if `--no-publish` (#473)
• Check package name availability in custom registry (#429)
• Fix incorrectly showing "Aborted!" message on successful publish (#471)
• 5.1.3
• Fix global detection for when Node.js was installed with Homebrew

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu[bot]]

Closing because this update has already been applied