ci: circle CI voter and release jobs

.circleci/config.yml

@@ -0,0 +1,57 @@
+version: 2.1
+jobs:
+  build-node15:
+    docker:
+      - image: circleci/node:15-browsers
+    working_directory: ~/repo
+    steps:
+      - checkout
+      - run: yarn
+      - run: yarn run ci
+
+  build-node14:
+    docker:
+      - image: circleci/node:14-browsers
+    working_directory: ~/repo
+    steps:
+      - checkout
+      - run: yarn
+      - run: yarn run ci
+
+  build-node12:
+    docker:
+      - image: circleci/node:12-browsers
+    working_directory: ~/repo
+    steps:
+      - checkout
+      - run: yarn
+      - run: yarn run ci
+
+  deploy-npm:
+    docker:
+      - image: circleci/node:14-browsers
+    working_directory: ~/repo
+    steps:
+      - checkout
+      - run: yarn --pure-lockfile
+      - run: yarn run ci
+      - run: echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
+      # To help debug when lerna detects changes to the working tree and fails the publish
+      - run: git status
+      - run: yarn run release:publish
+
+workflows:
+  version: 2
+  voter:
+    jobs:
+      - build-node12
+      - build-node14
+      - build-node15
+  release:
+    jobs:
+      - deploy-npm:
+          filters:
+            tags:
+              only: /^v[0-9]+(\.[0-9]+)*/
+            branches:
+              ignore: /.*/

.gitignore

@@ -56,4 +56,7 @@ typings/
 # build artifacts
 lib
 tsconfig.tsbuildinfo
-.rollup.cache
+.rollup.cache
+
+# jetbrains
+.idea

CONTRIBUTING.md

@@ -11,4 +11,13 @@ Our goal is to build a unique and welcoming community around this project. Code
 
 ### On the details of contributing
 
-As far as code style, repo management, tools, etc, ehh we can figure that out! Don't sweat it. Ask questions, and when you find answers, do your best to fill in any gaps in code documentation and in the Docusaurus docs, so that the next person doesn't encounter the same gaps.
+As far as code style, repo management, tools, etc, ehh we can figure that out! Don't sweat it. Ask questions, and when you find answers, do your best to fill in any gaps in code documentation and in the Docusaurus docs, so that the next person doesn't encounter the same gaps.
+
+### Release Process
+Performing a release requires push permissions to the repository.
+
+- Ensure you are on the master branch and synced with origin.
+- yarn run release:version
+- Follow the lerna CLI instructions and choose the new version number.
+- Track the newly pushed tag (/^v[0-9]+(\.[0-9]+)*/) build in the build system until successful completion.
+- Inspect the new artifacts published on npmjs.com, e.g:

package.json

@@ -40,6 +40,8 @@
     "typescript": "^4.0.3"
   },
   "scripts": {
+    "release:version": "lerna version",
+    "release:publish": "lerna publish from-git --yes",
     "ci": "lerna run ci && yarn run lint",
     "lint:fix": "eslint --fix '**/*.{ts,json}'",
     "lint": "eslint '**/*.{ts,json}'",