From 1b8aa062114c9d951bf8f4f6c2054b36630be6fd Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 14 Jul 2026 02:17:29 +0000
Subject: [PATCH] Version Packages

---
 .changeset/review-rc-body.md  | 5 -----
 workflows/review/CHANGELOG.md | 6 ++++++
 workflows/review/package.json | 2 +-
 workflows/review/review.md    | 2 +-
 4 files changed, 8 insertions(+), 7 deletions(-)
 delete mode 100644 .changeset/review-rc-body.md

diff --git a/.changeset/review-rc-body.md b/.changeset/review-rc-body.md
deleted file mode 100644
index 58acf69a..00000000
--- a/.changeset/review-rc-body.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"review": patch
----
-
-Always submit REQUEST_CHANGES with a non-empty body. Step 6 previously instructed the opposite ("a REQUEST_CHANGES verdict carries at least one blocking inline comment, so submit it with an empty body", dating to #197): GitHub rejects a REQUEST_CHANGES review event with an empty body, and under gh-aw v0.81.6 the safe-output flow posts the review event separately from the inline comments, so the comments do not make it non-empty. Observed live on the v1.5.0 behavior test (Khan/webapp#40793): the reviewer computed REQUEST_CHANGES correctly for two blocking findings, the submission failed with "Review body is required for REQUEST_CHANGES", and the PR was left with the inline comments as a COMMENTED review and no blocking verdict. The latent instruction survived this long because models usually filled the body anyway. The body's first line is now always `Changes requested — see inline comments.`, with the accountability section, note lines, and fingerprint stamp appended as before.
diff --git a/workflows/review/CHANGELOG.md b/workflows/review/CHANGELOG.md
index a2932353..678ebb78 100644
--- a/workflows/review/CHANGELOG.md
+++ b/workflows/review/CHANGELOG.md
@@ -1,5 +1,11 @@
 # review
 
+## 1.6.1
+
+### Patch Changes
+
+-   70c7560: Always submit REQUEST_CHANGES with a non-empty body. Step 6 previously instructed the opposite ("a REQUEST_CHANGES verdict carries at least one blocking inline comment, so submit it with an empty body", dating to #197): GitHub rejects a REQUEST_CHANGES review event with an empty body, and under gh-aw v0.81.6 the safe-output flow posts the review event separately from the inline comments, so the comments do not make it non-empty. Observed live on the v1.5.0 behavior test (Khan/webapp#40793): the reviewer computed REQUEST_CHANGES correctly for two blocking findings, the submission failed with "Review body is required for REQUEST_CHANGES", and the PR was left with the inline comments as a COMMENTED review and no blocking verdict. The latent instruction survived this long because models usually filled the body anyway. The body's first line is now always `Changes requested — see inline comments.`, with the accountability section, note lines, and fingerprint stamp appended as before.
+
 ## 1.6.0
 
 ### Minor Changes
diff --git a/workflows/review/package.json b/workflows/review/package.json
index c1432321..a8bfac3c 100644
--- a/workflows/review/package.json
+++ b/workflows/review/package.json
@@ -1,6 +1,6 @@
 {
     "name": "review",
-    "version": "1.6.0",
+    "version": "1.6.1",
     "dependencies": {
         "octokit": "5.0.5"
     }
diff --git a/workflows/review/review.md b/workflows/review/review.md
index da3400cb..3c7f522f 100644
--- a/workflows/review/review.md
+++ b/workflows/review/review.md
@@ -229,7 +229,7 @@ pre-agent-steps:
     uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5
     with:
       repository: Khan/actions
-      ref: review-v1.6.0
+      ref: review-v1.6.1
       path: gh-aw-review-lib
       persist-credentials: false