[TIMOB-13836] CLI: tag the source with <version> when publishing a version to global npm
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-06-04T20:55:11.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 12 JS, Release 3.2.0 |
| Components | CLI |
| Labels | n/a |
| Reporter | Michael Xia |
| Assignee | Chris Barber |
| Created | 2013-05-13T04:08:19.000+0000 |
| Updated | 2017-03-09T18:28:51.000+0000 |
Description
When a new version of CLI is released, e.g. 3.1.1, the corresponding source code should be tagged with 3.1.1. This is to help Studio implemnt TISTUD-4632.
We already tag modules with the version. Why do we need the 'v'? It breaks our convention. Can't you adapt to a tag without the 'v'?
We are going to leave the tagged versions in the format "X.Y.Z".
Re-opening as this request is for tagging the git source in addition to tagging the npm package.
We have created the following wiki page to document the npm publish steps: https://wiki.appcelerator.org/display/pe/NPM+Release+Process
Closing ticket as fixed.