Publishing should respect package.json's private value

Open pedrofaustino opened this issue 12 years ago • 3 comments

It seems that with default values (npm: true), grunt-release does not respect the value of the private key found on package.json. Even with private: true, grunt-release tries to publish it.

Is this as planned? We use grunt-release to automate our release process, but it's a private package.

Nov 06 '13 17:11 pedrofaustino

Aye, I agree on this one. Grunt release is a little shy on configuration.

Nov 20 '13 00:11 yoshuawuyts

Ah, good call we should add that.

On Tue, Nov 19, 2013 at 5:33 PM, Yoshua [email protected] wrote:

Aye, I agree on this one. Grunt release is a little shy on configuration.

— Reply to this email directly or view it on GitHubhttps://github.com/geddski/grunt-release/issues/57#issuecomment-28853610 .

Nov 20 '13 05:11 geddski

:+1:

Feb 02 '15 17:02 scottux