Fix release notes agent (#1061)

* Add instructions to create a full clone, not shallow one

Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com>

* Refresh other aw output

Co-Authored-By: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: SteveSandersonMS

.github/aw/actions-lock.json

@@ -1,19 +1,34 @@
 {
   "entries": {
+    "actions/checkout@v6.0.2": {
+      "repo": "actions/checkout",
+      "version": "v6.0.2",
+      "sha": "de0fac2e4500dabe0009e67214ff5f5447ce83dd"
+    },
+    "actions/download-artifact@v8.0.0": {
+      "repo": "actions/download-artifact",
+      "version": "v8.0.0",
+      "sha": "70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3"
+    },
     "actions/github-script@v8": {
       "repo": "actions/github-script",
       "version": "v8",
       "sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
     },
-    "github/gh-aw-actions/setup@v0.64.2": {
-      "repo": "github/gh-aw-actions/setup",
-      "version": "v0.64.2",
-      "sha": "f22886a9607f5c27e79742a8bfc5faa34737138b"
+    "actions/upload-artifact@v7.0.0": {
+      "repo": "actions/upload-artifact",
+      "version": "v7.0.0",
+      "sha": "bbbca2ddaa5d8feaa63e36b76fdaad77386f024f"
     },
-    "github/gh-aw-actions/setup@v0.65.5": {
+    "github/gh-aw-actions/setup@v0.67.4": {
       "repo": "github/gh-aw-actions/setup",
-      "version": "v0.65.5",
-      "sha": "15b2fa31e9a1b771c9773c162273924d8f5ea516"
+      "version": "v0.67.4",
+      "sha": "9d6ae06250fc0ec536a0e5f35de313b35bad7246"
+    },
+    "github/gh-aw/actions/setup@v0.52.1": {
+      "repo": "github/gh-aw/actions/setup",
+      "version": "v0.52.1",
+      "sha": "a86e657586e4ac5f549a790628971ec02f6a4a8f"
     }
   }
 }

.github/workflows/handle-bug.lock.yml

@@ -46,12 +46,18 @@ Use the GitHub API to fetch the release corresponding to `${{ github.event.input
 
 ### Step 1: Identify the version range
 
-1. The **new version** is the release tag: `${{ github.event.inputs.tag }}`
-2. Fetch the release metadata to determine if this is a **stable** or **prerelease** release.
-3. Determine the **previous version** to diff against:
+1. **Before any `git log`, `git show`, tag lookup, or commit-range query, first convert the workflow checkout into a full clone by running:**
+   ```bash
+   git fetch --prune --tags --unshallow origin || git fetch --prune --tags origin
+   ```
+   This is **mandatory**. The workflow checkout may be shallow, which can make tag ranges and commit counts incomplete or outright wrong. Do not trust local git history until this command succeeds.
+2. The **new version** is the release tag: `${{ github.event.inputs.tag }}`
+3. Fetch the release metadata to determine if this is a **stable** or **prerelease** release.
+4. Determine the **previous version** to diff against:
    - **For stable releases**: find the previous **stable** release (skip prereleases). Check `CHANGELOG.md` for the most recent version heading (`## [vX.Y.Z](...)`), or fall back to listing releases via the API. This means stable changelogs include ALL changes since the last stable release, even if some were already mentioned in prerelease notes.
    - **For prerelease releases**: find the most recent release of **any kind** (stable or prerelease) that precedes this one. This way prerelease notes only cover what's new since the last release.
-4. If no previous release exists at all, use the first commit in the repo as the starting point.
+5. If no previous release exists at all, use the first commit in the repo as the starting point.
+6. After identifying the range, verify it by listing the commits in `PREVIOUS_TAG..NEW_TAG`. If the local result still looks suspiciously small or inconsistent, do **not** proceed based on local git alone — use the GitHub tools as the source of truth for the commits and PRs in the release.
 
 ### Step 2: Gather changes