You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd nativescript-angular/nativescript-angular && git checkout release && git pull
93
+
```
94
+
#### If we prepare major or minor release, merge master in release branch else **skip this step**.
90
95
```
96
+
git merge --ff-only origin/master
97
+
```
98
+
*** Note: If there are commits in release branch which are not merged in master branch '-ff-merge' command will fail.
99
+
In this case the commits should be merge firstly from release in master branch as explained in section 'Merge changes from release into master' and then repeat step 1.
91
100
92
-
2. Add the following to your `.npmrc`:
101
+
2. Execute `npm i` to install dependencies:
102
+
```
103
+
cd nativescript-angular && npm i
104
+
```
105
+
3. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version:
106
+
```
107
+
npm --no-git-tag-version version [patch|minor|major] -m "release: cut the %s release"
108
+
```
109
+
or
93
110
```
94
-
tag-version-prefix=""
95
-
message="release: cut the %s release"
111
+
npm --no-git-tag-version version [version] --allow-same-version -m "release: cut the %s release"
96
112
```
113
+
NOTE: Check the changelog!!!
97
114
98
-
3. Create new branch for the release:
99
-
```bash
100
-
git checkout -b username/release-version
115
+
4. Create release-branch with change log
116
+
```
117
+
git checkout -b release-[version]
118
+
```
119
+
5. Add changes
101
120
```
121
+
git add changed-files
122
+
git commit -m "release: cut the %s release"
123
+
git push
124
+
```
125
+
NOTE: Make sure the PR is based on release branch
102
126
103
-
4. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version in the `package.json` file, tag the release and update the CHANGELOG.md:
104
-
```bash
105
-
npm version [patch|minor|major]
127
+
6. Merge PR into release branch.
128
+
129
+
7. The merge will produce package with rc tag in npm. If all checks have passed, publish official package. Usually the night builds will be triggered and the package will be ready to be released on the next day.
130
+
131
+
8. Don't forget to tag the release branch
132
+
```
133
+
git tag [version]
134
+
git push --tags
135
+
```
136
+
Only if needed to Tips to remove tags:
137
+
```
138
+
git push --delete origin [version]
139
+
git tag -d [version]
106
140
```
107
141
108
-
5. Push all the changes to your branch and create a pull request:
0 commit comments