Update NPM package version, and release notes (#1019)

CONTRIBUTING.md

@@ -42,16 +42,19 @@ repo.
     and at the commit that you want to tag as the next release (usually
     `@HEAD`).
 2.  Ensure that the [CHANGELOG](CHANGELOG.md) has a release summary entry for
-    v0.X.Y. If not, create one with a brief summary of breaking changes. (Change details are autogenerated by GitHub in a later step.)
-3.  Create the tags for v0.X.Y (we currently need two):
+    v0.X.Y. If not, create one with a brief summary of breaking changes. (Change
+    details are autogenerated by GitHub in a later step.)
+3. Update the Hugo module versions to v0.X.Y.
+4. Update the NPM package version in [package.json](package.json) to v0.X.Y.
+5.  Create the tags for v0.X.Y (we currently need two):
 
     ```console
     $ REL=v0.X.Y
     $ git tag $REL
     $ git tag dependencies/$REL
     ```
 
-4.  Push the new tags to the main repo (which is named `upstream` in my setup)
+6.  Push the new tags to the main repo (which is named `upstream` in my setup)
     either one by one or all together provided you have no other new tags
     defined. The following illustrates the latter, and does a dry run first:
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "docsy",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "repository": "github:google/docsy",
   "scripts": {
     "_cd:docs": "cd userguide &&",