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
{{ message }}
Repository navigation
Commit 451026f
Browse filesBrowse the repository at this point in the historyBrowse files
*** Note: If there are commits in release branch which are not merged in master branch '-ff-merge' command will fail.
231
+
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.
232
+
233
+
2. Execute `npm i` to install dependencies:
239
234
```
240
235
npm i
241
236
```
242
-
4. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version of `tns-platform-declarations`:
237
+
3. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version of `tns-platform-declarations`:
243
238
```
244
239
cd tns-platform-declarations
245
240
npm --no-git-tag-version version [major|minor|patch] -m "release: cut the %s release"
246
241
cd ..
247
242
```
248
243
249
-
5. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version of `tns-core-modules`,
250
-
tag the release and update the CHANGELOG.md.
251
-
In case we need to publish release version we need simply to use npm version x.x.x-rc
244
+
4. Execute [`npm version`](https://docs.npmjs.com/cli/version) to bump the version of `tns-core-modules`,
245
+
tag the release and update the CHANGELOG.md. Don't forget to check the auto-generated CHANGELOG.md
252
246
```
253
247
cd tns-core-modules
254
248
npm --no-git-tag-version version [major|minor|patch] -m "release: cut the %s release"
@@ -257,6 +251,11 @@ cd ..
257
251
6. Set correct version of **tns-core-modules-widgets** in tns-core-modules/package.json.
258
252
Usually tns-core-modules-widgets should already have been released and we need to set the official version.
259
253
254
+
7. Create release-branch with change log
255
+
```
256
+
git checkout -b release-[release-version]
257
+
```
258
+
260
259
7. Add changes
261
260
```
262
261
git add changed-files
@@ -268,13 +267,13 @@ git push
268
267
git tag release-version
269
268
git push --tags
270
269
```
271
-
9. Create a pull request. Replace env variables ${RELEASE_VERSION} and ${BRANCH} with their values
270
+
9. Create a pull request. Be careful to base your branch on the correct branch
272
271
```
273
-
curl -d '{"title": "release: cut the ${RELEASE_VERSION} release","body": "docs: update changelog","head": "${BRANCH}","base": "release"}' -X POST https://api.github.com/repos/NativeScript/NativeScript/pulls -H "Authorization: token ${GIT_TOKEN}"
272
+
curl -d '{"title": "release: cut the [release-version] release","body": "docs: update changelog","head": "${BRANCH}","base": "release"}' -X POST https://api.github.com/repos/NativeScript/NativeScript/pulls -H "Authorization: token ${GIT_TOKEN}"
274
273
```
275
274
10. Merge PR into release branch.
276
275
277
-
11. If all checks has passed publish package.
276
+
11. If all checks has passed publish package. Usually the night builds will be triggered and the package will be ready to be released on the next day.
0 commit comments