Update version for 1.6.0.pre1 pre-release #435
Merged
Conversation
This file contains hidden or 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
Signed-off-by: James Couball <jcouball@yahoo.com>
|
I added the 1.6.0.pre1 section to CHANGELOG.md |
perlun
approved these changes
Jan 20, 2020
AgoraSecurity
pushed a commit
to AgoraSecurity/ruby-git
that referenced
this pull request
Feb 21, 2020
Signed-off-by: James Couball <jcouball@yahoo.com>Signed-off-by: Agora Security <github@agora-security.com>
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.
Signed-off-by: James Couball jcouball@yahoo.com
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.
Description
Bump version to build a 1.6.0.pre1 release.
This is in preparation for the 1.6.0 release. Since it has been a while since the last release (1.5.0 Aug 18th, 2018), we have decided to put out a pre-release version of this gem (1.6.0.pre1) for people to test.
The maintainers will need to determine the release criteria for 1.6.0 and communicate this to the community in issue #434.
My hope is that after the 1.6.0 release, we can start to accept all the great contributions people have made.