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.
Coverage remained the same at 100.0% when pulling f82bed478016abc9155c0e95b4a0bfef5cc1feb1 on greenkeeper-yargs-6.3.0 into 3440cd9d61a9f0072749c620e57bf53f5123b584 on master.
Hello lovely humans,
yargs just published its new version 6.3.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 53 commits .
164efb6
chore: upgrade nyc
066613a
chore(release): 6.3.0
92aaa7c
docs: add new languages to supported locales (#681)
6b85cc6
fix(command): subcommands via commandDir() now supported for parse(msg, cb) (#678)
02c0970
chore: Moved breaking change from "features" to "breaking" in changelog (#677)
c05e36b
feat(locales): Add Thai locale file (#679)
004e70b
chore(release): 6.2.0
3fe9b8f
fix: stop applying parser to context object (#675)
81984e6
feat: Italian translations for 'did you mean' and 'aliases' (#673)
5615a82
feat: add new pt_BR translations (#674)
0cc6e5a
chore(release): 6.1.1
ae4bcd4
fix: freeze was not resetting configObjects to initial state; addressed performance issue raised by @nexdrew. (#670)
6a88f83
chore(release): 6.1.0
051b19a
chore: add read-pkg-up to greenkeeper ignore
f284c29
feat: reworking yargs API to make it easier to run in headless environments, e.g., Slack (#646)
There are 53 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade