Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 18 Jun 2015 01:19:00 +0000 (UTC)
From: "Steve Gill (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12838645.1434590282000.104417.1434590340401@Atlassian.JIRA>
In-Reply-To: <JIRA.12838645.1434590282000@Atlassian.JIRA>
References: <JIRA.12838645.1434590282000@Atlassian.JIRA>
 <JIRA.12838645.1434590282539@arcas>
Subject: [jira] [Created] (CB-9211) Look into using `npm version` in release
 process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Steve Gill created CB-9211:
------------------------------

             Summary: Look into using `npm version` in release process
                 Key: CB-9211
                 URL: https://issues.apache.org/jira/browse/CB-9211
             Project: Apache Cordova
          Issue Type: Improvement
          Components: Coho
            Reporter: Steve Gill
            Assignee: Steve Gill
            Priority: Minor


Whenever you type npm version to bump the version number in your package.json file and add the tag in git, any preversion package scripts that are defined in package.json will be run beforehand and postversion will be run afterwards.

Lets see if it makes sense to incorporate this into our release process to replace some of the steps we do now. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org