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 merge
Merges this PR once your tests are passing and conflicts are resolved
@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 83.14% when pulling 67db4f030b0ca2c19ecd31a4ff00085f06461e85 on depfu/update/npm/yargs-13.1.0 into 98656ad1bc06c2a13cc5cf28f3bc82522d4783c6 on master.
Coverage remained the same at 83.14% when pulling 67db4f030b0ca2c19ecd31a4ff00085f06461e85 on depfu/update/npm/yargs-13.1.0 into 98656ad1bc06c2a13cc5cf28f3bc82522d4783c6 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 (^12.0.2 → ^13.1.0) · Repo · Changelog
Release Notes
13.1.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
chore(release): 13.1.0
test: add tests for alias behavior, based on conversations today (#1291)
chore: slight refactor of approach being used, add support for per-command
feat: add applyBeforeValidation, for applying sync middleware before validation
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