[chore] auto-deploy with CI

.circleci/config.yml

@@ -1,9 +1,18 @@
+# Javascript Node CircleCI 2.0 configuration file
+#
+# Check https://circleci.com/docs/2.0/language-javascript/ for more details
+#
+
 version: 2
+
+defaults: &defaults
+  working_directory: ~/fabrix
+  docker:
+    - image: circleci/node:10.0.0
+
 jobs:
-  build:
-    working_directory: ~/fabrix
-    docker:
-      - image: circleci/node:10.0.0
+  test:
+    <<: *defaults
     steps:
       - checkout
       - run:
@@ -35,3 +44,34 @@ jobs:
           prefix: coverage
       - store_test_results:
           path: test-results.xml
+      - persist_to_workspace:
+          root: ~/fabrix
+          paths: .
+  deploy:
+    <<: *defaults
+    steps:
+      - attach_workspace:
+          at: ~/fabrix
+      - run:
+          name: Authenticate with registry
+          command: echo "//registry.npmjs.org/:_authToken=$npm_TOKEN" > ~/fabrix/.npmrc
+      - run:
+          name: Publish package
+          command: npm publish
+
+workflows:
+  version: 2
+  test-deploy:
+    jobs:
+      - test:
+          filters:
+            tags:
+              only: /^v.*/
+      - deploy:
+          requires:
+            - test
+          filters:
+            tags:
+              only: /^v.*/
+            branches:
+              ignore: /.*/

.github/CONTRIBUTING.md

@@ -82,7 +82,7 @@ In case of doubt, open an issue in the [issue tracker](https://github.com/fabrix
 
 ## Publishing Releases
 
-All releases are tagged and published by the [Fabrix.js Maintainers](https://github.com/orgs/fabrix-app/teams) automatically via [Cicle-CI](https://circleci.com/gh/fabrix-app/fabrix). For a patch release, the deployment process is as follows:
+All releases are tagged and published by the [Fabrix Maintainers](https://github.com/orgs/fabrix-app/teams) automatically via [Cicle-CI](https://circleci.com/gh/fabrix-app/fabrix). For a patch release, the deployment process is as follows:
 
 1. Tag a release
 ```sh

LICENSE

@@ -1,7 +1,7 @@
 The MIT License (MIT)
 
 Copyright (c) 2018 CST <[email protected]>
-                   2018 Scott Wyatt <[email protected]>
+              2018 Scott Wyatt <[email protected]>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal