chore: update lerna config (#59)

* fix: remove publish script in package.json (yarn publish in already taken)

* chore: update lerna config for lerna version

* docs: update README publishing section

Author: P0labrD

README.md

@@ -37,7 +37,7 @@ All you have to do is the versioning of the packages you want to publish.
 
 > You need to be on the main branch and have the repo write access to publish a new version.
 
-Run `yarn publish` to start the process. It will run the command `yarn lerna version --conventional-commits` which will prompt you to select the packages you want to publish and the version bump for each of them.
+Run `yarn lerna version` to start the process. It will run the command `yarn lerna version --conventional-commits --no-private`.
 
 Lerna will prompt you to select the version bump for each package. It will also generate the changelog for each package based on the commit messages since the last version.
 
@@ -53,6 +53,8 @@ Changes:
  - @bam.tech/eslint-plugin: 1.0.0 => 1.1.0
 ```
 
+It will then push a tagged commit `chore(release): Publish` which will then trigger the Github Workflow to publish the new version of each package to NPM.
+
 ## Running commands
 
 - `yarn lerna run start`: run the 'start' script in all packages (currently only present in `example-app`),

lerna.json

@@ -5,7 +5,10 @@
   "packages": ["packages/*"],
   "command": {
     "version": {
-      "noPrivate": true
+      "private": false,
+      "message": "chore(release): Publish",
+      "conventionalCommits": true,
+      "allowBranch": "main"
     }
   }
 }

package.json

@@ -1,9 +1,6 @@
 {
   "name": "root",
   "private": true,
-  "scripts": {
-    "publish": "lerna version --conventional-commits --no-private"
-  },
   "workspaces": [
     "packages/*",
     "example-app"