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)
Coverage remained the same at 82.941% when pulling 8d2d08c0b7ce651f28ee8a3ea09c1b1f64bd42a1 on depfu/update/npm/yargs-16.0.3 into 2229001a59abd958d705a5ee6a97f8bab27806e9 on master.
Coverage remained the same at 82.941% when pulling 8d2d08c0b7ce651f28ee8a3ea09c1b1f64bd42a1 on depfu/update/npm/yargs-16.0.3 into 2229001a59abd958d705a5ee6a97f8bab27806e9 on master.
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?
✳️ yargs (^15.0.1 → ^16.0.3) · Repo · Changelog
Release Notes
16.0.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
chore: release 16.0.3 (#1748)
fix: move yargs.cjs to yargs to fix Node 10 imports (#1747)
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