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.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 34 commits .
6adbe55
chore(release): 4.8.1
c77c080
fix: pull in @nexdrew's fixes to yargs-parser (#560)
063a866
fix: positional arguments were not being handled appropriately by parse() (#559)
8d7585c
fix: add config lookup for .implies() (#556)
3c2e479
fix(commandDir): make dir relative to caller instead of require.main.filename (#548)
38b64f0
coveralls@2.11.10 breaks build 🚨 (#551)
fea7e0b
fix: cache pkg lookups by path to avoid returning the wrong one (#552)
eb1e185
chore: cut release
9d4a5a8
docs: switch to the ridiculous appveyor URL you get when you switch project orgs
76eb66e
chore(release): 4.8.0
e058c87
fix: ignore invalid package.json during read-pkg-up (#546)
8d6ad6e
feat: builder is now optional for a command module (#545)
2609b2e
fix: lazy-load package.json and cache. get rid of pkg-conf dependency. (#544)
588a8c1
Merge pull request #543 from yargs/greenkeeper-nyc-7.0.0
4d6153a
chore(package): update nyc to version 7.0.0
There are 34 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade