The version 11.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of yargs.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 100.0% when pulling 78d661b5cc025a4a9f7e70ca5fc679bf2465ae73 on greenkeeper/yargs-11.0.0 into 4e162c829e416db44cdcf32b819e5a326e52639b on master.
Coverage remained the same at 100.0% when pulling 78d661b5cc025a4a9f7e70ca5fc679bf2465ae73 on greenkeeper/yargs-11.0.0 into 4e162c829e416db44cdcf32b819e5a326e52639b on master.
Coverage remained the same at 100.0% when pulling 78d661b5cc025a4a9f7e70ca5fc679bf2465ae73 on greenkeeper/yargs-11.0.0 into 4e162c829e416db44cdcf32b819e5a326e52639b on master.
Version 11.0.0 of yargs was just published.
The version 11.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of yargs.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 3 commits.
57a39cb
chore(release): 11.0.0
a3ddacc
feat: requiresArg is now simply an alias for nargs(1) (#1054)
2b56812
fix: Set implicit nargs=1 when type=number requiresArg=true (#1050)
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: