add updates before first automated release

Author: chris-pearce

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changes to backpack.css 🎒
 
+## 2.2.0 (April 02, 2020)
+
+- Improve the publishing experience ([#22](https://github.com/chris-pearce/backpack.css/issues/22))
+
 ## 2.1.0 (March 29, 2020)
 
 - Set up linting ([#9](https://github.com/chris-pearce/backpack.css/issues/9))

CONTRIBUTING.md

@@ -131,10 +131,11 @@ Tests will be added eventually for everything that can have a visual test ([see]
 
 backpack.css uses [np](https://github.com/sindresorhus/np) for publishing.
 
-If you have permission to publish a new version, apply the following steps:
+If you have permission to publish a new version, apply the following steps on the `master` branch:
 
 1. Add all new changes to [`CHANGELOG.md`](CHANGELOG.md), making sure to follow the existing format.
-2. Run: `yarn np <version>` where `<version>` is one of the semantic versioning release types: **patch**, **minor**, or **major**.
+2. Run: `git add -A` then `git commit -m "updates before release"`.
+3. Run: `yarn release`.
 
 ## Linting
 

package.json

@@ -20,8 +20,10 @@
     "lint": "stylelint \"**/*.css\"",
     "build": "yarn bundle && yarn autoprefix",
     "prebuild": "yarn clean",
-    "version": "yarn build && git add CHANGELOG.md",
-    "postversion": "yarn clean"
+    "prerelease": "yarn build",
+    "release": "np",
+    "postrelease": "yarn clean",
+    "test": "echo \"No test specified\""
   },
   "browserslist": [
     "last 4 versions and > 0.5%",