chore: add in changesets to handle changelog creation and publishing

Author: crutchcorn

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "restricted",
+  "baseBranch": "master",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

CONTRIBUTING.md

@@ -0,0 +1,30 @@
+For each change made (anything not marked as a "chore"), run the following command:
+```
+yarn changeset add
+```
+
+This will allow you to do the following:
+
+1) Select impacted packages
+2) Add a related message
+3) Notify what type of package bump is required (major, minor, patch)
+
+-------
+
+# Releasing
+
+When a maintainer is ready to publish, run the following command to generate a changelog:
+
+```
+yarn changeset version
+```
+
+You should then verify, using your Git CLI or Git GUI, that the CHANGELOG is correct, everything is up-to-date, and that you're ready to release!
+
+> **Do not create a commit manually after "yarn changeset version"**.
+
+Then, once you've ran `version`, run the following command to publish to NPM:
+
+```
+yarn changeset publish
+```

package.json

@@ -3,9 +3,9 @@
   "version": "0.0.0",
   "private": true,
   "workspaces": {
-   "packages": [
-     "packages/*"
-   ],
+    "packages": [
+      "packages/*"
+    ],
     "nohoist": [
       "**/plop-pack-fancy-comments"
     ]
@@ -45,5 +45,8 @@
   },
   "lint-staged": {
     "*.js": "eslint --cache --fix"
+  },
+  "dependencies": {
+    "@changesets/cli": "^2.22.0"
   }
 }