fix(build): now updating version

now updating version in package.json

CONTRIBUTING.md

@@ -28,12 +28,13 @@ Before you submit your Pull Request (PR) consider the following guidelines:
 * Commit your changes using a descriptive commit message that follows our
   [commit message conventions](#commit-message-guidelines). Adherence to these conventions
   is necessary because release notes are automatically generated from these messages.
-by running  followed by npm run commit.
      ```shell
      # stage your changes 
      git add .
      # use git-cz interactive helper tool to commit
      npm run commit
+     # or use following command if you install commitizen globally   
+     git cz
      ```
   Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
 

package.json

@@ -96,6 +96,7 @@
     ],
     "prepare": [
       "@semantic-release/changelog",
+      "@semantic-release/npm",
       "@semantic-release/git"
     ],
     "publish": [
@@ -123,13 +124,13 @@
     "@angular/pwa": "^0.7.5",
     "@angular/router": "^6.1.7",
     "@angular/service-worker": "^6.1.7",
-    "@nestjs/common": "^5.3.5",
-    "@nestjs/core": "^5.3.4",
+    "@nestjs/common": "^5.3.6",
+    "@nestjs/core": "^5.3.6",
     "@nestjs/elasticsearch": "^0.1.2",
-    "@nestjs/microservices": "^5.3.5",
-    "@nestjs/passport": "^5.0.1",
+    "@nestjs/microservices": "^5.3.6",
+    "@nestjs/passport": "^5.0.2",
     "@nestjs/swagger": "^2.5.1",
-    "@nestjs/typeorm": "^5.2.0",
+    "@nestjs/typeorm": "^5.2.1",
     "@nestjs/websockets": "^5.3.1",
     "@ngx-formly/core": "^5.0.0-beta.6",
     "@ngx-formly/material": "^5.0.0-beta.6",

stories/howto.md

@@ -37,13 +37,19 @@ How to migrate project to newer versions?
 
 How to commit code?
 
-```bash
-git status
-# if all is good
-git add .
-# now commit
-`git cz` # or npm run commit
-```
+ ```bash
+ git status
+ # stage your changes 
+ git add .
+ # use git-cz interactive helper tool to commit
+ npm run commit
+ # or use following command if you install commitizen globally   
+ git cz
+ ```
+
+> Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+
+
 
 How to Cut a Release?
 
@@ -56,7 +62,7 @@ https://adrianperez.codes/enforcing-commit-conventions/
 https://medium.com/@schalkneethling/automate-package-releases-with-semantic-release-and-commitizen-d7d4c337f04f
 
 ```bash
-export GH_TOKEN=<my_guthyb_token>
+export GH_TOKEN=<my_github_token>
 export CI=true
 npm run semantic-release
 ```