Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow [patch | minor | major | ....] as version for release command #19

Closed
sstok opened this issue Jan 25, 2017 · 0 comments
Closed

Allow [patch | minor | major | ....] as version for release command #19

sstok opened this issue Jan 25, 2017 · 0 comments

Comments

@sstok
Copy link
Member

sstok commented Jan 25, 2017

When creating a new release I should be able to use the next "version fragment" automatically
hubkit minor and get the next logical minor version for this branch.

The command already validates if there are gaps so getting the next version should not be a problem.

This should support patch, minor, major, beta, rc and alpha. And increase that fragment.
For beta this means the current beta version is increased, if there there is no current beta release then increase the minor version and set beta to 1.

@sstok sstok closed this as completed in #23 Feb 11, 2017
sstok added a commit that referenced this issue Feb 11, 2017
This PR was merged into the 1.0-dev branch.

Discussion
----------

Allow `alpha | beta | rc | patch | minor | major | stable` as version for release command.

Closes #19

Commits
-------

0ad43b2 Add Version::increase() to get increased version
3aeaca3 Allow releases based on relative versions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant