-
Notifications
You must be signed in to change notification settings - Fork 3
Update yargs to the latest version 🚀 #63
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 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 9.0.1 of yargs just got published.
The version 9.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 24 commits.
d1b23f3chore(release): 9.0.1ac8088bfix: implications fails only displayed once (#954)73be236chore(release): 9.0.00e0c58dfix: strict mode should not fail for hidden options (#949)c240661fix: address bug with handling of arrays of implicationsabdc7dafeat: allow implies and conflicts to accept array values (#922)a9f03e7feat: allow parse with no arguments as alias for yargs.argv (#944)792564dfeat: to allow both undefined and nulls, for benefit of TypeScript (#945)71c7ec7fix: exclude positional arguments from completion output (#927)a40cbc9refactor: ES6ify (#937)767d0d0refactor: Use native Object.assign (#936)a2c0fefdocs: correct typos in example.md (#934)1d56df3chore(package): Change engine node version to >=4 (#926)ab592c3docs: add link to community slack (#930)1ef44e0feat: enable .help() and .version() by default (#912)There are 24 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 🌴