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 ea14b465c0a9d4d3a1c02e8927a38d91735d5791 on greenkeeper-yargs-6.1.1 into e4065fece67a7b50ef778b4ade4c440a28cd6d47 on master.
Hello lovely humans,
yargs just published its new version 6.1.1.
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 43 commits .
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)
b1cabae
feat(command): add camelcase commands to argv (#658)
aa966c5
fix(locales): change some translations (#667)
22adb18
fix(locales): conform hi locale to y18n.__n expectations (#666)
9290912
feat(locales): add Hindi translations
be92327
feat(locales): add Hungarian translations
072fd45
feat: Turkish translations for 'did you mean' and 'aliases' (#660)
8ba2462
russian translation for the locales (#663)
a618b08
Merge pull request #656 from dgrcode/translation/spanish
c015d2c
Add "aliases" and "did you mean %s?"
1059ed2
Korean translations for 'did you mean' and 'aliases'
There are 43 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade