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
Copy file name to clipboardExpand all lines: README.md
+29
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,36 @@ You can develop and test locally your modified package by running `npm link`. Th
99
99
Commit messages must follow conventions, please use these guidelines: https://github.com/conventional-changelog/conventional-changelog-angular/blob/master/convention.md
100
100
101
101
Any new feature must be unit tested. The following `npm` tasks are available:
102
+
102
103
-`npm test` Will run all tests and print tests results along code coverage.
103
104
-`npm run test-ci` Will watch for any files changes and run all tests
104
105
105
106
Code coverage report is generated in `/coverage/lcov-report` folder
107
+
108
+
## Release process
109
+
------------------
110
+
Release is made with `standard-version` of `conventional-changelog`:
111
+
112
+
```
113
+
npm run release
114
+
```
115
+
116
+
The following jobs will be ran:
117
+
118
+
- Bumping version in package.json file
119
+
- Outputting changes to CHANGELOG.md (based on commit messages)
120
+
- Committing package.json and CHANGELOG.md
121
+
- Adding a new tag for targeted release
122
+
123
+
124
+
Once your local master branch is ready, just run the following command:
125
+
```
126
+
npm run publish
127
+
```
128
+
129
+
The following jobs will be ran:
130
+
131
+
- Pushing commit and tag to the remote master branch
132
+
- Publish the package to npm registry
133
+
134
+
> Publishing on npm registry requires a registered user. Please read [Publishing npm packages](https://docs.npmjs.com/getting-started/publishing-npm-packages) for more details.
0 commit comments