Add support for pre-release versions #43
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
jcouball
force-pushed
the
pre_release_releases
branch
from
5d31d60
to
802acf4
Compare
jcouball
force-pushed
the
pre_release_releases
branch
from
802acf4
to
ecffd32
Compare
![codeclimate[bot]](https://avatars.githubusercontent.com/in/9403?s=60&v=4){kind=small}
|
|
||
| # Validates a set of options after the options have been fully initialized | ||
| # @api private | ||
| class CommandLineOptionsValidator |
There was a problem hiding this comment.
Class CommandLineOptionsValidator has 21 methods (exceeds 20 allowed). Consider refactoring.
|
Code Climate has analyzed commit 3b0d80f and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 100.0% (0.0% change). View more on Code Climate. |
Merged
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.
Add the ability for
create-github-releaseto create a release with a pre-release version asdefined in the Semver 2.0.0 spec.
An example of a pre-release version is
1.0.0-beta.1.Pre-release versions have a lower precedence than their associated normal version.
This means the pre-release version sorts before the associated release version. For
example,
1.0.0-beta.1comes before1.0.0. A pre-release version indicates thatthe version is unstable and might not yet satisfy the intended compatibility
requirements as denoted by its associated normal version
This gem limits pre-release versions to the form
MAJOR.MINOR.PATCH-PRERELEASEwherePRERELEASEcan ONLY have the following form:TYPE.DIGITS.TYPEis any textstring allowed in the Semver 2.0.0 spec and is typically 'alpha', 'beta', 'pre',
'rc', etc.
DIGITSis a numeric identifier that does not include leading zeroes.Create the first pre-release version for the next minor release
If the current release is
1.0.0, the command to create a pre-release for the next minor version where the pre-release type isalphawould be:This will create a release whose version is
1.1.0-alpha.1.Create subsequent pre-releases
If the current release is
1.1.0-alpha.1, the command to create the nextalpharelease would be:This will create a release whose version is
1.1.0-alpha.2.Change the pre-release type
If the current release version is
1.1.0-alpha.2, the command to create the release where the pre-release type isbetawould be:This will create a release whose version is
1.1.0-beta.1.Create the release after pre-release
If the current release version is
1.1.0-beta.1, the command to create the normal / non-pre-release would be:This will create a release whose version is
1.1.0.