XS⚠️ ◾ [Autogenerated] Release v1.6.4 (#565)

Autogenerated release for PR Metrics v1.6.4. This includes the latest
dependency updates.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: muiriswoulfe

.github/workflows/release-phase-1.yml

@@ -21,4 +21,4 @@ jobs:
     with:
       major: 1
       minor: 6
-      patch: 4
+      patch: 5

.github/workflows/support/release-phase-1-comment.md

@@ -7,13 +7,9 @@ Before completing this PR, the license information **must** be updated.
 1. Wait for the entire PR build to complete.
 1. Use the internal Microsoft Component Governance tooling to update [`src/LICENSE.txt`][licensetxt] with the automatically generated license information.
 
-   1. At the top of the page, click `main` and select "Edit tracked branches".
-   1. Click the wrench icon to right of `refs/pull/PR_ID/merge` where `PR_ID` is the PR number.
-   1. In the flyout, select "Track this branch". Ensure the "PR Metrics – PR" pipeline is selected. Click "Submit".
-   1. At the top of the page, click `microsoft/PR-Metrics` to navigate back to the original page.
-   1. Change the `main` branch to `refs/pull/PR_ID/merge` where `PR_ID` is the PR number. **It is very important that this is selected correctly or the wrong license information will be generated.**
-   1. Use Notice > Configure to ensure that only the `dependencies` from [`package.json`][packagejson] are included and that the `devDependencies` are excluded.
-   1. Use Notice > Download to generate the file. Select Pipeline "PR" and Format "Plain Text". Click "Download".
+   1. Switch to the Components tab.
+   1. At the top of the page, click `main` and select `refs/pull/PR_ID/merge` where `PR_ID` is the PR number. **It is vital that this is selected correctly or the wrong license information will be generated.**
+   1. Use Notice > Download to generate the file. Select Pipeline "PR Metrics – Prod (Validation)" and Format "Plain Text". Click "Download".
    1. Add the downloaded content to the end of [`src/LICENSE.txt`][licensetxt]. Note that the ordering of licenses may change.
    1. If the download dialog includes any notice indicating that license information could not be located at [Clearly Defined][clearlydefined], 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:
 
@@ -32,4 +28,3 @@ Before completing this PR, the license information **must** be updated.
 [clearlydefined]: https://clearlydefined.io/
 [clearlydefinedharvest]: https://clearlydefined.io/harvest
 [licensetxt]: https://github.com/microsoft/PR-Metrics/blob/main/src/LICENSE.txt
-[packagejson]: https://github.com/microsoft/PR-Metrics/blob/main/package.json

.github/workflows/support/release-trigger.txt

@@ -1 +1 @@
-1.6.3
+1.6.4

README.md

@@ -113,7 +113,7 @@ The default input values are expected to be appropriate for most builds.
 Therefore, the following YAML definition is recommended:
 
 ```YAML
-uses: microsoft/PR-Metrics@v1.6.3
+uses: microsoft/PR-Metrics@v1.6.4
 name: PR Metrics
 env:
   PR_METRICS_ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -123,7 +123,7 @@ continue-on-error: true
 If you wish to modify the inputs, YAML akin the to the following can be used:
 
 ```YAML
-uses: microsoft/PR-Metrics@v1.6.3
+uses: microsoft/PR-Metrics@v1.6.4
 name: PR Metrics
 env:
   PR_METRICS_ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}

dist/index.js

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/resjson.json",
   "loc.description": "Augments pull request titles to let reviewers quickly determine PR size and test coverage.",
   "loc.description.comment": "The description of the task.",
-  "loc.friendlyName": "PR Metrics v1.6.3",
+  "loc.friendlyName": "PR Metrics v1.6.4",
   "loc.friendlyName.comment": "The name of the task.",
   "loc.helpMarkDown": "[More information](https://aka.ms/PRMetrics/README)",
   "loc.helpMarkDown.comment": "The Markdown-formatted help text of the task.",