XS⚠️ ◾ [Autogenerated] Release v1.5.4

[muiriswoulfe]

Autogenerated release for PR Metrics v1.5.4.

[github-actions[bot]]

PR Metrics

✔ Thanks for keeping your pull request small. ⚠️ Consider adding additional tests.		Lines
Product Code	8
Test Code	1
Subtotal	9
Ignored Code	272
Total	281

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!

[github-actions[bot]]

Required License Update

Before completing this PR, the license information must be updated.

Note that if lockfileVersion is set to 3 (rather than 2) in package-lock.json, the license information may not be correctly generated. In this case, you will need to change lockfileVersion to 2 and rerun the build.

1. Wait for the entire PR build to complete.

2. Use the internal Microsoft Component Governance tooling to update src/LICENSE.txt with the automatically generated license information.

   1. At the top of the page, click main and select "Edit tracked branches".
   2. Click the wrench icon to right of refs/pull//merge.
   3. In the flyout, select "Track this branch". Ensure the "PR" pipeline is selected. Click "Submit".
   4. At the top of the page, click microsoft/PR-Metrics to navigate back to the original page.
   5. Change the main branch to refs/pull//merge. It is very important that this is selected correctly or the wrong license information will be generated.
   6. Use Notice > Configure to ensure that only the dependencies from package.json are included and that the devDependencies are excluded.
   7. Use Notice > Download to generate the file. Select Pipeline "PR" and Format "Plain Text". Click "Download".
   8. Add the downloaded content to the end of src/LICENSE.txt. Note that the ordering of licenses may change.

   9. If the download dialog includes any notice indicating that license information could not be located at Clearly Defined, you will need to add the information to that source. To do this, expand the drop down menu in the dialog to reveal the problematic dependencies. For each dependency:

      1. Navigate to the Clearly Defined Harvest page.
      2. In the first search box, select "NpmJS".
      3. In the second search box, select the dependency name.
      4. In the "Pick an npm version" box, select the appropriate version.
      5. Click "Harvest".

      It is also possible to add all dependencies to the page and click "Harvest" afterwards to harvest all license information simultaneously.

      Wait some time for harvesting to complete and try regenerating the license information at the Component Governance page. Repeat the process until all license information is available.

3. Commit all the changes to your branch, updating the PR.