Updating version number to 0.9.6

docs/code-owner-docs.md

@@ -132,7 +132,9 @@ The `.scripts/build.sh` script, which is run by calling `npm run build` from the
 When enough changes (bugs and new features) have been merged into the `develop` branch to warrant a new version, create a release with a new version number.
 
 1. Create a PR from the `develop` branch into `main` branch.
-1. Once that PR is merged into `main`, checkout `main` locally and pull to get the latest changes. Then, update the version number in `package.json` in your local `main` branch and commit, then push back up to GitHub. (Release creation will fail if the version in `package.json` is not the same as the version you are creating.)
+1. Once that PR is merged into `main`, checkout `main` locally and pull to get the latest changes. Then, update the version number in `package.json` in your local `main` branch.
+   - Release creation will fail if the version in `package.json` is not the same as the version you are creating. 
+1. Run `npm run build` to update the `package-lock.json` and commit, then push back up to GitHub.
 1. Use the [Release page](https://github.com/KCarlile/guitar-diagrams-js/releases) to create a new release.
 
 ### Versioning

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@KCarlile/guitar-diagrams-js",
-  "version": "0.9.5",
+  "version": "0.9.6",
   "description": "Guitar Diagrams JS is an open source JavaScript library for drawing guitar chords and scales on an HTML5 canvas.",
   "homepage": "https://github.com/KCarlile/guitar-diagrams-js#readme",
   "exports": {