This repository has been archived by the owner on Sep 7, 2020. It is now read-only.
Update yargs to version 5.0.0 🚀 #624
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MoOx
force-pushed
the
greenkeeper-yargs-5.0.0
branch
3 times, most recently
from
129a208
to
0e30cc8
Compare
MoOx
force-pushed
the
greenkeeper-yargs-5.0.0
branch
from
0e30cc8
to
3f2d2ef
Compare
|
Close in favor of #757 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
yargs just published its new version 5.0.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 ✨
You rock!
🌴
The new version differs by 131 commits .
985b1bachore(release): 5.0.054c4a34tests: remove osx from CI, until Travis fixes OSX serversc190855docs: added gitter badge (#593)cec3279chore(package): update string-width to version 1.0.2 (#591)afbe771Merge pull request #590 from yargs/greenkeeper-nyc-8.1.0bd16353chore(package): update nyc to version 8.1.0f9b0ed4perf: defer requiring most external libs until needed (#584)59474dcfeat: adds recommendCommands() for command suggestions (#580)59a830bchore(package): update lodash.assign to version 4.2.0 (#587)76ade7achore(package): update yargs-parser to version 3.2.0 (#588)1d53ccbfeat: add coerce api (#586)0aaa68bfeat: apply default builder to command() and apply fail() handlers globally (#583)927810cfeat: interpret demand() numbers as relative to executing command (#582)882a127feat: update yargs-parser to version 3.1.0 (#581)be65728feat: apply .env() globally (#553)There are 131 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade