-
Notifications
You must be signed in to change notification settings - Fork 11
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
Create version bumping task #16
Comments
@Matrim-Cauthon, should we go ahead and use
We could however go ahead and use it programmatically, but there are alternatives to this.
I tried both approach, and it would work as expected. One thing to note though is that when using Another possible approach is by using the ordinary
The |
Note that we don't just need to bump the minor version. This will be true especially when we do true semver, which will happen when we get to a stable version --- 1.X.X or higher. I'm biased towards a gulp-based approach since we're using that to define our most-commonly used tasks anyway. How it's implemented under the hood is not important as long as we're able to specify how to bump the version number 👍 |
The npm version minor was just an example. So we'll just go ahead and do this:
This way, we will be the ones to manually commit the changes, and manually add the tag. I believe this is OK since we usually bump the versions on the develop or release branch, while we tag the versions on our master branch. The command would be like this:
Without the flags, it would behave as What this gulp task would do is execute the |
For a quicker release process. This should update both npm and bower version numbers.
If possible, we should also automatically add the version number as a comment in the build.
The text was updated successfully, but these errors were encountered: