-
Notifications
You must be signed in to change notification settings - Fork 13
Update yargs to the latest version 🚀 #26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Version 8.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits0.
false See the full diff |
Version 9.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Version 10.0.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 33 commits.
There are 33 commits in total. See the full diff |
Version 10.1.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Version 11.0.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 5 commits.
See the full diff |
Version 12.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 46 commits.
There are 46 commits in total. See the full diff |
|
|
Update to this version instead 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
|
|
|
|
|
|
|
|
Version 7.1.0 of yargs just got published.
The version 7.1.0 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.
Commits
The new version differs by 37 commits .
e7359d6chore(release): 7.1.0c357412docs: switch to conventional commits badge [ci skip] (#850)17e89bdfix: we shouldn't output help if we've printed a prior help-like message (#847)50c9acdchore: add editorconfig (#848)360e301fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)fde0564feat: add support for numeric commands (#825)c748dd2fix: fix demandOption no longer treats 'false' as truthy (#829)e0b4efbtest: Made unit test passing with node-chakracore8756a3cchore(release): 7.0.2fa86602chore: fix test messageb3eb2fefix: populating placeholder arguments broke validation82c7a4euse console.log instead of util.print, fix #8134df3a10chore(release): 7.0.19c03fa4fix: --help with default command should print top-level help (#810)5334370docs: env vars now take precedence over config file/objects (#808)There are 37 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴