Update yargs: 17.0.1 → 17.1.1 (minor)

[depfu]

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 (17.0.1 → 17.1.1) · Repo · Changelog

Release Notes

17.1.1

Bug Fixes

• positional array defaults should not be combined with provided values (#2006) (832222d)

17.1.0

Features

• update Levenshtein to Damerau-Levenshtein (#1973) (d2c121b)

Bug Fixes

• coerce middleware should be applied once (#1978) (14bd6be)
• implies should not fail when implied key's value is 0, false or empty string (#1985) (8010472)
• positionals should not overwrite options (#1992) (9d84309)
• strict should fail unknown arguments (#1977) (c804f0d)
• wrap(null) no longer causes strange indentation behavior (#1988) (e1871aa)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 15 commits:

• chore: release 17.1.1 (#2007)
• fix: positional array defaults should not be combined with provided values (#2006)
• chore: release 17.1.0 (#1984)
• build: use denoland/setup-deno (#1991)
• fix: wrap(null) no longer causes strange indentation behavior (#1988)
• chore(deps): update dependency @types/mocha to v9 (#1993)
• fix: positionals should not overwrite options (#1992)
• fix: implies should not fail when implied key's value is 0, false or empty string (#1985)
• fix: coerce middleware should be applied once (#1978)
• feat: update Levenshtein to Damerau-Levenshtein (#1973)
• fix: strict should fail unknown arguments (#1977)
• i18n: Update zh_TW.json (#1976)
• docs: add config header & add .argv union & header for choices (#1958)
• chore(deps): update dependency mocha to v9 (#1962)
• refactor: use modern array helpers, etc

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

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)