[ALOY-660] Alloy: tag the source with <version> when publishing a version to global npm
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2013-05-14T15:34:04.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 1.1.3, 2013 Sprint 10 |
| Components | n/a |
| Labels | n/a |
| Reporter | Michael Xia |
| Assignee | Unknown |
| Created | 2013-05-13T04:09:57.000+0000 |
| Updated | 2018-03-07T22:25:36.000+0000 |
Description
When a new version of alloy 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.
[~tlukasavage] Yes, that's correct.
Added tag "1.1.3" to the alloy github repo in reference to the newly released alloy 1.1.3-alpha npm module. The tag can be referenced here: https://github.com/appcelerator/alloy/tree/1.1.3