gruntjs/grunt — pull request #717 by geddesign (2013-03-10 08:03:37+00:00)
Title: Use grunt-release for automating Grunt releases with Grunt

I'm jumping in to help on the development of Grunt and the 30 or so contrib plugins. When I was working on the Angular grunt build I noticed that Grunt and these libs sometimes hadn't pushed their latest changes to npm, or bumped the version, or created a git tag, etc. Which is understandable, the release process for a node lib is pretty tedious:

1. bump the version in your package.json file.
* stage the package.json file's change.
* commit that change with a message like "release 0.6.22".
* create a new git tag for the release.
* push the changes out to github.
* also push the new tag out to github.
* publish the new version to npm.

It's easy to forget steps (I do all the time). Luckily there's this cool new tool you may have heard of, named Grunt, that lets us automate things like this. I wrote a [grunt-release](https://github.com/geddesign/grunt-release) that does all these steps automatically with one command:

`grunt release`
or
`grunt release:minor`
or
`grunt release:major`

I suggest we add this to the Grunt project and all the contrib plugins (I have push access to those, so I can do that part). Then we can `grunt release` all the things.