Bump protocol to v17.0.1 (#882)

CHANGELOG.md

@@ -1,4 +1,4 @@
-# HEAD
+# 17.0.1
 
 ## Bug Fixes
 

README.md

@@ -124,7 +124,7 @@ name. To publish a release to NPM, use the following steps:
     (use [Semantic Versioning](https://semver.org/) to determine what the new version number
     should be).
 3. Update the package README [assets/package/README.md](https://github.com/mozilla/protocol/blob/main/assets/package/README.md).
-4. Run `npm install` to update the package-lock.json file.
+4. Update the package `version` number in the root [package.json](https://github.com/mozilla/protocol/blob/main/package.json) file and then run `npm install` to update the `package-lock.json` file.
 5. Submit a pull request with your changes (or commit directly to `main` if you
     have permission). Once the changes have been merged to main:
 6. Tag a new release. You can do this either using [Git tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging),

assets/package/README.md

@@ -20,7 +20,11 @@ Install package with NPM and add it to your dependencies:
 </tr>
 <tr>
 <td>Version</td>
-<td><a href="https://github.com/mozilla/protocol/blob/master/CHANGELOG.md">17.0.0</a></td>
+<td><a href="https://github.com/mozilla/protocol/blob/master/CHANGELOG.md">17.0.1</a></td>
+</tr>
+<tr>
+<td>Releases</td>
+<td><a href="https://github.com/mozilla/protocol/releases/">View all</a></td>
 </tr>
 </table>
 

assets/package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mozilla-protocol/core",
-  "version": "17.0.0",
+  "version": "17.0.1",
   "description": "A design system for Mozilla's websites.",
   "repository": {
     "type": "git",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "protocol",
-  "version": "17.0.0",
+  "version": "17.0.1",
   "private": true,
   "author": "Mozilla",
   "description": "A design system for Mozilla's websites.",