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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ yargs (16.0.3 → 16.1.0) · Repo · Changelog
Release Notes
16.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
chore: release 16.1.0 (#1779)
chore(deps): update `cliui`, `escalade`, `y18n`, `yargs-parser` (#1783)
feat: expose hideBin helper for CJS (#1768)
build: update to loatest release-please
build(linter): switch to gts/standardx for linting (#1777)
fix(exports): node 13.0-13.6 require a string fallback (#1776)
chore(deps): update dependency gts to v3 (#1775)
fix(deno): update types for deno ^1.4.0 (#1772)
docs: document onFinishCommand option (#1769)
test: throw on warning when in tests
docs(terminology): update terminology (#1766)
docs: document how to bundle yargs with webpack/ncc (#1757)
docs: add deprecate to documentation (#1762)
fix(positional): positional strings no longer drop decimals (#1761)
fix(modules): module path was incorrect (#1759)
fix: make positionals in -- count towards validation (#1752)
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