sungard-labs / grunt-sg-release Goto Github PK

Get the current version number of the module and output it before asking for the new release version number.

That will make people sure of what version number they are releasing, and will also allow us to provide a default value increasing the patch number (like grunt-bump does by default).

Hi folks

Specifying a releaseVersion and developVersion on command line works fine with [email protected], but it seems that [email protected] changed the handling of the arguments passed with the command-line interface (using [email protected] in both cases).

To make it more concrete, the following command works fine with [email protected]:

grunt release --releaseVersion 1.3.0 --developVersion 1.4.0-rc

but with [email protected] it fails with the following error message:

Error: Task "1.3.0" not found.

Best regards
Pierre

Currently the task is not proper failing in case it encounters problems along the way. We should add grunt.fail() calls along the task to make sure the user has proper feedback and that the task does not keep running if anything is wrong.

Our subtasks should probably require one another.

[needs validation]

Provide an interface making questions to the user to figure out the version number.

We could first provide a prompt list displaying something like:

> This package is currently at version 1.0.2 (develop branch)
>
> What have been changed since the last release?
> 1) An incompatible API change (such as break changes) [2.0.0]
> 2) Added functionality (still backwards compatible) [1.1.0]
> 3) Bug fixes (still backwards compatible) [1.0.3]
> 4) Let me input my version manually!

Hi there,
luckily I found this package before adding all of what this does to grunt-bump!

I have a question though... How can I perform a hotfix release with this package? Meaning, instead of starting with branching of develop, rather branch of master, pause in the middle, do my hotfix changes on this hotfix branch and then merge to back to master + merge to develop?

When setting a custom tagName, in this case %VERSION%, the tag push fails.

I believe the culprit is:
gitHelper.push(grunt, process.cwd(), options.pushTo, 'v' + grunt.option('releaseVersion'), done);
since the 'v' is hard coded.