-
Notifications
You must be signed in to change notification settings - Fork 1
Update yargs to the latest version 🚀 #6
base: master
Are you sure you want to change the base?
Conversation
1 similar comment
Version 7.0.2 just got published. |
Version 7.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits .
See the full diff. |
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.0.1 of yargs just got published.
The version 7.0.1 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 25 commits .
4df3a10chore(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)bc56468docs: a couple small twaks to the CHANGELOG57dc7b5chore(release): 7.0.0f3f074bfix: positional arguments of sub-commands threw strict() exception (#805)a607061fix: console.warn() rather than throwing errors when api signatures are incorrect (#804)d78a0f5feat: introduces support for default commands, using the '*' identifier (#785)8a992f5fix: errors were not bubbling appropriately from sub-commands to top-level (#802)07e39b7fix: running parse() multiple times on the same yargs instance caused exception if help() enabled (#790)48575cdfix: context variables are now recognized in strict() mode (#796)49a93fcfix: use path.resolve() to support node 0.10 (#797)3280dd0feat: allow provided config object to extend other configs (#779)e0fbbe5fix: pull in yargs-parser with modified env precedence (#787)0997288fix: context should override parsed argv (#786)There are 25 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 🌴