build: improve lerna publish process (#3082)

CONTRIBUTING.md

@@ -103,11 +103,7 @@ Here are some things to keep in mind as you file pull requests to fix bugs, add
 - Make sure the tests pass with `yarn test`
 - Run `git clean -fdx` - this will ensure unneeded build files (and potentially sensitive files) are not included in the npm package.
 - Ensure that you are logged into npm via command line (`npm login`)
-- `lerna publish --force-publish`
-  - **running this command without the `--force-publish` flag will only publish packages that have changes since
-    last release**.
-  - for beta releases, select `custom prerelease` when prompted, and enter `y` to increment the beta version.
-  - version numbers should be an un-prefixed [semantic version](https://semver.org/) number (e.g. `6.0.0-beta.67)
+- Run `yarn lerna:publish`, which will run the `lerna publish` command with a necessary set of flags.
   - The script will then ask you for your `npm` OTP password.
   - The script will commit the changes automatically. Run `git log` to confirm that the changes have been
     committed.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "electron-forge",
-  "version": "6.0.1",
+  "version": "0.0.0-development",
   "private": true,
   "license": "MIT",
   "engines": {
@@ -16,6 +16,7 @@
     "docs:generate": "yarn docs:plugin && node --max-old-space-size=8192 -r ts-node/register ./tools/gen-docs.ts",
     "docs:plugin": "cd ./tools/doc-plugin && yarn build",
     "docs:deploy:build": "yarn docs",
+    "lerna:publish": "lerna publish --force-publish --conventional-commits --no-changelog",
     "lint": "prettier --check . && eslint .",
     "lint:fix": "prettier --write .",
     "link:prepare": "lerna exec -- node ../../../tools/silent.js yarn link --link-folder ../../../.links --silent --no-bin-links",