Closed jasonkarns closed 9 years ago
Heh, that was less added than I was expecting. :smile: A while ago I created https://www.npmjs.org/package/grunt-prompt just for the purpose of asking patch
, minor
, major
, or pre-release
for an unreleased and eventually abandoned version bump grunt task.
I'll get this in later today.
Yeah, there isn't much to the grunt-release configuration because all of the defaults are pretty much exactly what you want. Of course, if any of the options need tweaked, the grunt config will need to actually have an initConfig
call, but so long as the defaults work, simply loading the release task is sufficient.
Sorry, didn't have time to check this out today, hopefully tomorrow.
worked great, thank you!
see grunt-release documentation at its repo: https://github.com/geddski/grunt-release
Added the bare minimum amount of configuration for the gruntfile.
quick overview: grunt-release bumps the version number in package.json, adds, commits and tags the change in git, pushes to the default configured remote, and publishes to npm, all in a single command
key points:
grunt release
orgrunt release:patch
increment the patch numbergrunt release:minor
increments the minor version numbergrunt release:major
increments the major version numberPlenty more config options available