NOJIRA add npm audit exclusion (#322)

.nsprc

@@ -1,4 +1,5 @@
 {
+  "GHSA-67hx-6x53-jw92": "@babel/traverse - devDependency, no risk given our usage",
   "GHSA-j8xg-fqg3-53r7": "word-wrap - devDependency, no risk given our usage",
   "GHSA-c2qf-rxjj-qqgw": "semver - devDependency, no risk given our usage",
   "GHSA-7fh5-64p2-3v2j": "postcss - devDependency, no risk given our usage",

CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ## [Unreleased]
 
+## [5.50.0] - 2023-10-16
+
+### Changed
+
+- Updated npm audit exclusions
+
 ## [5.49.0] - 2023-09-27
 
 ### Changed

CONTRIBUTING.md

@@ -112,10 +112,8 @@ To do this and run the BackstopJS tests in one command, you can run the followin
     env BACKSTOP_TEST_HOST={your local machines ip address} npm run test:backstop 
     ```
 
-
-* If you're running on a Mac with Apple Silicon (eg. M1 processor), you should uncomment the workarounds in [`backstop-config.js`](tasks/gulp/backstop-config.js)
-to use a compatible version of backstop/chromium, to work around [this known issue](https://github.com/garris/BackstopJS/issues/1300).
-
+* If backstop tests hang, you should try lowering `asyncCaptureLimit` and/or `asyncCompareLimit` in [`backstop-config.js`](tasks/gulp/backstop-config.js).
+The tests will take longer to run, but might no longer hang.
 
 * If you run into a problem where some of your visual regression tests are failing due to unrelated changes (for instance on screens you may not have touched or updated),
 you may want to delete the `node_modules` folder from the root of the project and then re-run command.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "hmrc-frontend",
-  "version": "5.49.0",
+  "version": "5.50.0",
   "description": "Design patterns for HMRC frontends",
   "scripts": {
     "start": "gulp dev",