Create version bumping task

[mikeybanez]

Create version bumping task

@Matrim-Cauthon, should we go ahead and use npm version minor by using npm.commands? I found this on NPM website:

Although npm can be used programmatically, its API is meant for use by the CLI only, and no guarantees are made regarding its fitness for any other purpose. If you want to use npm to reliably perform some task, the safest thing to do is to invoke the desired npm command with appropriate arguments.

We could however go ahead and use it programmatically, but there are alternatives to this.

• One is by updating the package.json and bower.json files
• Or, by executing a CLI command through nodejs using require('child_process').exec

I tried both approach, and it would work as expected. One thing to note though is that when using npm version, it would auto-tag it and auto-commit it (thus requiring the current branch to be clean) unless we add a --no-git-tag-version flag and --force flag to prevent it from auto-committing and auto-tagging.

Another possible approach is by using the ordinary npm version on the CLI itself, but adding a 'scripts' attribute on the package.json:

"scripts": {
  "preversion": "gulp test",
  "version": "gulp version && git add",
  "postversion": "git push && git push --tags"
}

The gulp version should build the file and add the necessary comments on the compiled xjs.js. Also, it could version up the bower file programmatically.

[mikeybanez]

should we go ahead and use npm version minor

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:

One is by updating the package.json and bower.json files

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:

gulp version --major|minor|patch --up|down

Without the flags, it would behave as gulp version --minor --up

What this gulp task would do is execute the default task first, then execute the version up/down task.