fix: versioning (#92)

* fix: versioning

* ci: add renovate

Author: adamdehaven

.github/workflows/publish.yaml

@@ -4,6 +4,8 @@ on:
   push:
     branches:
       - main
+      - alpha
+      - beta
 
 jobs:
   run-tests:

.github/workflows/test.yaml

@@ -4,6 +4,8 @@ on:
   pull_request:
     branches:
       - main
+      - alpha
+      - beta
 
   # Allow workflow to be called by another workflow
   workflow_call:
@@ -43,7 +45,8 @@ jobs:
 
       - name: Publish package preview
         id: package-preview
-        if: github.event_name == 'pull_request'
+        # Do not run for `alpha` or `beta` branches
+        if: github.event_name == 'pull_request' && github.actor != 'renovate[bot]' && !contains(github.head_ref || github.ref_name, 'alpha') && !contains(github.head_ref || github.ref_name, 'beta')
         env:
           NPM_TOKEN: ${{ secrets.NPM_TOKEN_PUBLIC_PUBLISH }}
         run: |

README.md

@@ -426,7 +426,7 @@ This will trigger the Commitizen interactive prompt for building your commit mes
 
 [Lefthook](https://github.com/evilmartians/lefthook) is used to manage Git Hooks within the repo.
 
-- A `commit-msg` hook is automatically setup that enforces commit message stands with `commitlint`, see [`lefthook.yml`](./lefthook.yaml)
+- A `commit-msg` hook is automatically setup that enforces commit message stands with `commitlint`, see [`lefthook.yaml`](./lefthook.yaml)
 - A `pre-push` hook is used that runs `eslint` before allowing you to push your changes to the repository
 
 Additionally, CI will use `commitlint` to validate the commits associated with a PR in the `Lint and Validate` job.