Preface

This is basically the release workflow defined by Gulp as a plugin to avoid code duplication,

For more info: https://github.com/gulpjs/gulp/blob/master/docs/recipes/automate-release-workflow.md

What it does?

Bump version in package.json, it follows SemVer semantic versioning, by default the patch version is bumped, but can be changed to release a minor or major version as well via a CLI param. (see below)
Update the CHANGELOG.md file with a link to the commits in between the previous and current version.
Commit the changes in current workspace.
Push the changes to the master branch.
Create and push a tag that correspond to the new version.

Usage

npm install --save-dev gulp-release-flows

Create a gulpfile.js in your project with:

// add to gulpfile.js
var gulp = require('gulp');

// pass along an *optional* config, if needed
require('gulp-release-flows')({
  sources: ['./bower.json', './package.json'],
  branch: 'master',
  bump: 'patch',
  message: 'Release %VERSION%',
  tag: null // The new version number. If null or not specified, will be retrieved from './package.json'.
});

To see all imported tasks, run:

gulp -T

To release, run:

gulp build:release

This will bump the patch version, minor / major can be bumped by the following command:

gulp build:release --bump minor

gulp build:release --bump major

You can also bump to a specific release version using the following command:

gulp build:release --tag 0.1.0-beta.3

admin-ch/gulp-release-flows

Preface

Usage