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)
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
5.2.1
5.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