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.
Coverage remained the same at 83.041% when pulling 70bc5b0642bb056b3017f0f7d787b2ae2aee9180 on depfu/update/npm/yargs-12.0.1 into 03a02a4f73d15d10555260339288de1090f68d26 on master.
We've upgraded a dependency and all tests pass. \o/
You should probably take a good look at this before merging this pull request, of course.
What changed?
✳️ yargs ( → 12.0.1) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 7 commits:
chore(release): 12.0.1
chore: explicit update of yargs-parser
chore: bump engines to Node.js 6.x (#1169)
chore: bump decamelize & find-up (#1168)
docs: add info about installing @next version, see #1134 (#1165)
docs: fix breaking change note in CHANGELOG.md (#1166)
docs: fix typo in CHANGELOG
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
.