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.
Hello lovely humans,
yargs just published its new version 4.8.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 40 commits .
eb1e185chore: cut release9d4a5a8docs: switch to the ridiculous appveyor URL you get when you switch project orgs76eb66echore(release): 4.8.0e058c87fix: ignore invalid package.json during read-pkg-up (#546)8d6ad6efeat: builder is now optional for a command module (#545)2609b2efix: lazy-load package.json and cache. get rid of pkg-conf dependency. (#544)588a8c1Merge pull request #543 from yargs/greenkeeper-nyc-7.0.04d6153achore(package): update nyc to version 7.0.0ed86b78fix: we now respect the order of _ when applying commands (#537)e6cf29edocs: added documentation about commands not inheriting configurations (#526)20d4b8afeat(command): derive missing command string from module filename (#527)365fb9afix: drop unused camelcase dependency fixes #516 (#525)5904d5cMerge pull request #524 from yargs/patch-10f8faa7fix: keep both zh and zh_CN until yargs@5.xb299dfffeat: add .commandDir(dir) to API to apply all command modules from a relative directory (#494)There are 40 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade