release: generate notes from git log, with RELEASE_NOTES.md override

Shared scripts/build-release-notes.sh emits Markdown release notes for a
given tag, bucketing commits by their prefix (feat / fix / docs /
installer / release / ci / vendor / chore / other).  If a hand-written
RELEASE_NOTES.md exists at repo root it's used verbatim instead — useful
when a particular release deserves a curated summary.

Both the CI workflow and scripts/release.sh now call this shared
generator, so automated and manual releases produce identical notes.
GitHub's built-in generate_release_notes was a bad fit: it synthesizes
from PR titles, and this repo commits directly to main.

Also set fetch-depth: 0 + fetch-tags: true on the release job's checkout
so `git log <prev>..HEAD` actually has history to walk.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: yysjasmine

.github/workflows/release.yml

@@ -77,11 +77,15 @@ jobs:
     needs: [build-windows, build-macos]
     runs-on: ubuntu-latest
     steps:
-      # Checkout so we can grab linux/install.sh for the Linux download.
-      # Nothing to build for Linux — install.sh bootstraps itself by
-      # cloning agent_pack on the user's machine, same shape as the
-      # curl | bash one-liner in the README.
+      # Checkout full history + tags so build-release-notes.sh below can
+      # diff against the previous tag.  linux/install.sh is also grabbed
+      # from this checkout and staged as a release asset (no build step —
+      # it bootstraps itself on the user's machine, same shape as the
+      # curl | bash one-liner in the README).
       - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          fetch-tags: true
 
       - name: Download Windows artifact
         uses: actions/download-artifact@v4
@@ -120,12 +124,22 @@ jobs:
         # Cover all three platforms' downloads.
         run: sha256sum AgentPack-* > SHA256SUMS
 
+      - name: Build release notes
+        # Delegates to scripts/build-release-notes.sh — same script is used
+        # by scripts/release.sh for local releases, so CI and manual
+        # releases produce identical notes.  Honors a hand-written
+        # RELEASE_NOTES.md at repo root when present.
+        run: |
+          ./scripts/build-release-notes.sh "${{ steps.tag.outputs.tag }}" > RELEASE_NOTES_BODY.md
+          echo "---- Release notes ----"
+          cat RELEASE_NOTES_BODY.md
+
       - name: Create / update Release
         uses: softprops/action-gh-release@v2
         with:
           tag_name: ${{ steps.tag.outputs.tag }}
           name: Agent Pack ${{ steps.tag.outputs.tag }}
-          generate_release_notes: true
+          body_path: RELEASE_NOTES_BODY.md
           # fail_on_unmatched_files keeps us honest if a build artifact
           # silently went missing before upload.
           fail_on_unmatched_files: true

scripts/build-release-notes.sh

@@ -0,0 +1,87 @@
+#!/usr/bin/env bash
+# build-release-notes.sh — Emit release notes for <tag> to stdout.
+#
+# Usage: build-release-notes.sh <tag>
+#
+# Resolution order:
+#   1. If ./RELEASE_NOTES.md exists at repo root, print it verbatim and exit.
+#      Use this to override for releases that deserve a hand-crafted summary.
+#   2. Otherwise synthesize Markdown from `git log <prev>..HEAD`, bucketing
+#      commits by the "type:" prefix we already use (feat / fix / docs / ci
+#      / installer / release / vendor / chore).  Unprefixed commits fall
+#      into "Other".
+#   3. If no previous v* tag exists, treat this as the first release and
+#      list the entire history.
+#
+# Callers:
+#   - .github/workflows/release.yml (CI release notes)
+#   - scripts/release.sh            (local `gh release create` uploader)
+#
+# Exits non-zero only on unexpected git failures; an empty commit range
+# still produces a valid (if short) notes body.
+
+set -euo pipefail
+
+[ $# -ge 1 ] || { echo "Usage: $0 <tag>" >&2; exit 2; }
+TAG="$1"
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
+REPO_SLUG="${GITHUB_REPOSITORY:-SenseTime-FVG/agent_pack}"
+
+# Hand-written override wins.
+if [ -f "$PROJECT_ROOT/RELEASE_NOTES.md" ]; then
+    cat "$PROJECT_ROOT/RELEASE_NOTES.md"
+    exit 0
+fi
+
+cd "$PROJECT_ROOT"
+
+# Previous tag = newest v* tag that isn't the one we're releasing.  Empty
+# string means "no prior release — walk the whole history".
+prev="$(git tag --list 'v*' --sort=-v:refname | grep -v "^${TAG}$" | head -n1 || true)"
+
+if [ -n "$prev" ]; then
+    range="${prev}..HEAD"
+    header="Changes since [$prev](https://github.com/${REPO_SLUG}/releases/tag/$prev)"
+else
+    range="HEAD"
+    header="Initial release."
+fi
+
+echo "$header"
+echo
+
+# Bucket recognized prefixes into titled sections, in a stable order so
+# diffs between consecutive releases look consistent.
+for group in \
+    "feat|Features" \
+    "fix|Bug Fixes" \
+    "docs|Documentation" \
+    "installer|Installer" \
+    "release|Release" \
+    "ci|CI" \
+    "vendor|Vendored Changes" \
+    "chore|Chores"; do
+    prefix="${group%|*}"
+    title="${group#*|}"
+    body="$(git log --no-merges --pretty=format:"- %s (%h)" "$range" \
+            | grep -E "^- ${prefix}(\([^)]+\))?:" || true)"
+    if [ -n "$body" ]; then
+        echo "### $title"
+        echo
+        echo "$body"
+        echo
+    fi
+done
+
+# Anything that didn't match a known bucket.  Useful when someone commits
+# without a prefix — it still shows up, just under "Other".
+other="$(git log --no-merges --pretty=format:"- %s (%h)" "$range" \
+         | grep -vE "^- (feat|fix|docs|installer|release|ci|vendor|chore)(\([^)]+\))?:" || true)"
+if [ -n "$other" ]; then
+    echo "### Other"
+    echo
+    echo "$other"
+    echo
+fi

scripts/release.sh

@@ -122,16 +122,24 @@ else
     git push origin "$TAG"
 fi
 
-# Default release notes come from the git log since the previous tag; if
-# the caller wants custom notes they pass --notes-file themselves.
+# Default release notes are produced by scripts/build-release-notes.sh —
+# same generator the CI workflow uses, so local and CI releases look
+# identical.  The caller can still override with --notes-file pointing at
+# their own file, in which case we skip generation.
 HAS_NOTES=0
 for f in "${GH_FLAGS[@]}"; do
     case "$f" in
         --notes|--notes-file|--generate-notes) HAS_NOTES=1 ;;
     esac
 done
+NOTES_TMP=""
 if [ "$HAS_NOTES" -eq 0 ]; then
-    GH_FLAGS+=(--generate-notes)
+    NOTES_TMP="$(mktemp -t agent-pack-release-notes.XXXXXX)"
+    # shellcheck disable=SC2064
+    trap "rm -f '$NOTES_TMP'" EXIT
+    note "Building release notes via scripts/build-release-notes.sh"
+    "$SCRIPT_DIR/build-release-notes.sh" "$TAG" > "$NOTES_TMP"
+    GH_FLAGS+=(--notes-file "$NOTES_TMP")
 fi
 
 note "Creating release $TAG with ${#FILES[@]} asset(s)"