Update commander to the latest version 🚀 #1257
Merged
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
xPaw
added
the
Type: Dependencies
xPaw
approved these changes
Jun 24, 2017
astorije
approved these changes
Jun 25, 2017
matburnham
pushed a commit
to matburnham/lounge
that referenced
this pull request
Sep 6, 2017
…r-2.10.0 Update commander to the latest version 🚀
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Version 2.10.0 of commander just got published.
The version 2.10.0 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 commander.
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.
Release Notes
Release V2.10.0--descriptionCommits
The new version differs by 50 commits.
8870675version bump 2.10.098e66bc#330 make .option defaultValue and fn and .version flag optionald674384Merge pull request #639 from abetomo/update_version_to_be_tested45ce032Remove io.jsb888282Add version 55ac0439Do not test older versions579f670Do not test older versions4c7c1cfAdd new version8049258Do not test older versions9bfc4ebMerge pull request #610 from xcatliu/patch-1648629fMerge pull request #619 from Nepomuceno/patch-120493bbOn SemVer you do not start from 0.0.18a4f1adFix require arguments in README.md3367806Merge pull request #585 from simeg/simeg-patch-1ff501a1Merge pull request #593 from junajan/patch-1There are 50 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴