Merge pull request #119 from datacrafts-io/fix/semantic-release

fix(releases): add npm token to publish on npm

Author: cxspxr

.github/workflows/release.yml

@@ -23,4 +23,5 @@ jobs:
       - name: Release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
         run: npx semantic-release@17

.releaserc.json

@@ -0,0 +1,13 @@
+{
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    "@semantic-release/github",
+    [
+      "@semantic-release/npm",
+      {
+        "npmPublish": true
+      }
+    ]
+  ]
+}

README.md

@@ -100,6 +100,11 @@ Supports:
 
     In order to commit in a conventional style conveniently you may run `npm run commit`.
 
+## :warning: Disabling publishing to npm
+
+There is a file [.releaserc.json](.releaserc.json) where you can disable publishing your project
+to npm on every new semantic release by setting `npmPublish` option to `false`
+
 ## 🎓 Learning Gatsby
 
 Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.org/). Here are some places to start:

package.json

@@ -1,7 +1,7 @@
 {
   "name": "gatsby-opinionated-starter",
   "description": "A very opinionated TypeScript netlify-ready gatsby starter",
-  "version": "1.1.0",
+  "version": "1.1.0-semantically-versioned",
   "author": "Yaroslav Kasperovych <ilovewindows96@gmail.com>",
   "dependencies": {
     "@types/react-helmet": "6.1.0",