This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of yargs.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 100.0% when pulling 6cdd0888c4029ec2aef51bd4dca72b2000a2965b on greenkeeper-yargs-7.1.0 into e4065fece67a7b50ef778b4ade4c440a28cd6d47 on master.
Hello lovely humans,
yargs just published its new version 7.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of yargs. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 113 commits .
e7359d6
chore(release): 7.1.0
c357412
docs: switch to conventional commits badge [ci skip] (#850)
17e89bd
fix: we shouldn't output help if we've printed a prior help-like message (#847)
50c9acd
chore: add editorconfig (#848)
360e301
fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)
fde0564
feat: add support for numeric commands (#825)
c748dd2
fix: fix demandOption no longer treats 'false' as truthy (#829)
e0b4efb
test: Made unit test passing with node-chakracore
8756a3c
chore(release): 7.0.2
fa86602
chore: fix test message
b3eb2fe
fix: populating placeholder arguments broke validation
82c7a4e
use console.log instead of util.print, fix #813
4df3a10
chore(release): 7.0.1
9c03fa4
fix: --help with default command should print top-level help (#810)
5334370
docs: env vars now take precedence over config file/objects (#808)
There are 113 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.