List fixed issues in release notes (#54)

Author: KSemenenko

.github/workflows/deploy-github-pages.yml

@@ -314,10 +314,13 @@ jobs:
 
     permissions:
       contents: write
+      issues: read
 
     steps:
       - name: Checkout
         uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
 
       - name: Download release artifact
         uses: actions/download-artifact@v8.0.1
@@ -336,6 +339,98 @@ jobs:
 
           echo "release_asset=$release_asset" >> "$GITHUB_OUTPUT"
 
+      - name: Build release notes with fixed issues
+        id: release_notes
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          RELEASE_TAG: ${{ needs.prepare_release.outputs.release_tag }}
+          RELEASE_TITLE: PrompterOne ${{ needs.prepare_release.outputs.release_version }}
+        run: |
+          set -euo pipefail
+
+          notes_path="$RUNNER_TEMP/release-notes.md"
+          previous_tag="$(
+            gh release list \
+              --exclude-drafts \
+              --limit 50 \
+              --json tagName \
+              --jq ".[] | select(.tagName != \"$RELEASE_TAG\") | .tagName" \
+              | head -n 1
+          )"
+
+          if [ -n "$previous_tag" ] && git rev-parse --verify "${previous_tag}^{commit}" >/dev/null 2>&1; then
+            commit_range="${previous_tag}..${GITHUB_SHA}"
+            range_label="${previous_tag}...${RELEASE_TAG}"
+          else
+            commit_range="${GITHUB_SHA}"
+            range_label="Initial release range ending at ${GITHUB_SHA}"
+          fi
+
+          mapfile -t issue_numbers < <(
+            git log --format='%B' "$commit_range" \
+              | grep -Eo '#[0-9]+' \
+              | tr -d '#' \
+              | sort -n \
+              | uniq
+          )
+
+          issues_file="$RUNNER_TEMP/release-issues.md"
+          {
+            echo "## Fixed Issues"
+            echo
+
+            issue_count=0
+            for issue_number in "${issue_numbers[@]}"; do
+              issue_json="$(
+                gh api "repos/${GH_REPO}/issues/${issue_number}" \
+                  --jq 'select(.pull_request == null) | {number, title, url: .html_url}' \
+                  2>/dev/null || true
+              )"
+
+              if [ -z "$issue_json" ]; then
+                continue
+              fi
+
+              issue_title="$(jq -r '.title' <<<"$issue_json")"
+              issue_url="$(jq -r '.url' <<<"$issue_json")"
+              echo "- [#${issue_number}](${issue_url}) ${issue_title}"
+              issue_count=$((issue_count + 1))
+            done
+
+            if [ "$issue_count" -eq 0 ]; then
+              echo "_No linked GitHub issues were found in commits for this release._"
+            fi
+
+            echo
+            echo "_Issue range: ${range_label}_"
+          } > "$issues_file"
+
+          if [ -n "$previous_tag" ]; then
+            generated_notes="$(
+              gh api "repos/${GH_REPO}/releases/generate-notes" \
+                -f tag_name="$RELEASE_TAG" \
+                -f target_commitish="$GITHUB_SHA" \
+                -f previous_tag_name="$previous_tag" \
+                --jq '.body'
+            )"
+          else
+            generated_notes="$(
+              gh api "repos/${GH_REPO}/releases/generate-notes" \
+                -f tag_name="$RELEASE_TAG" \
+                -f target_commitish="$GITHUB_SHA" \
+                --jq '.body'
+            )"
+          fi
+
+          {
+            echo "$generated_notes"
+            echo
+            cat "$issues_file"
+          } > "$notes_path"
+
+          echo "release_notes=$notes_path" >> "$GITHUB_OUTPUT"
+
       - name: Create or update release tag and GitHub Release
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -344,13 +439,16 @@ jobs:
           RELEASE_TITLE: PrompterOne ${{ needs.prepare_release.outputs.release_version }}
         run: |
           release_asset="${{ steps.release_asset.outputs.release_asset }}"
+          release_notes="${{ steps.release_notes.outputs.release_notes }}"
           if gh release view "$RELEASE_TAG" >/dev/null 2>&1; then
             gh release upload "$RELEASE_TAG" "$release_asset" --clobber
-            gh release edit "$RELEASE_TAG" --title "$RELEASE_TITLE"
+            gh release edit "$RELEASE_TAG" \
+              --title "$RELEASE_TITLE" \
+              --notes-file "$release_notes"
           else
             gh release create "$RELEASE_TAG" "$release_asset" \
               --title "$RELEASE_TITLE" \
-              --generate-notes \
+              --notes-file "$release_notes" \
               --target "$GITHUB_SHA"
           fi
 

AGENTS.md

@@ -134,6 +134,7 @@ Rule format:
 - Stakeholder feedback issues should be interpreted as additive feature or presentation requests by default; do not remove existing behavior from wording such as "replace", "remove", or "rename" unless the user explicitly confirms deletion.
 - When a CI test job fails, times out, or is cancelled, the workflow summary must still state which tests failed or that the run ended before per-test failure data was available; do not leave browser-suite failures represented only by generic job annotations.
 - Do not add or raise CI timeout settings as a fix for browser-suite instability or slow runs; fix the underlying failure path cleanly instead of masking it with workflow or step timeouts.
+- GitHub Releases must include a fixed-issues section generated from the commits included since the previous release; collect referenced GitHub issue numbers from commit messages and render issue number, title, and link in the release notes instead of relying only on generic auto-generated notes.
 - For TUnit reporting in GitHub Actions, prefer TUnit's built-in HTML report and the documented `actions/github-script` runtime exposure step over repo-local custom summary scripts or ad-hoc log parsers.
 - GitHub Actions test jobs must use the repo `tests/dotnet-test-progress.rsp` response file and enable TUnit coverage for every runnable test suite so CI measures the same minimal, non-ANSI test output and coverage signal expected locally; do not configure detailed per-test `Standard output` or empty `Error output` blocks as the default log format.
 - Public web hosting is split by role: the standalone PrompterOne app in this repo must publish on `app.prompter.one`, while the marketing landing site for `prompter.one` lives in the separate `PrompterOne-LandingPage` repository.