refactor(scripts): rename prepare-release.sh to prepare-github-releas… (#4099)

Author: SimonRastikian

.cliffignore

@@ -1,5 +1,5 @@
 # Commits to exclude from the changelog (read by git-cliff via cliff.toml,
-# invoked from scripts/ops/prepare-release.sh and the manual flow in RELEASES.md).
+# invoked from scripts/ops/prepare-github-release.sh and the manual flow in RELEASES.md).
 # The block below is the 502 commits from the threshold-signatures repo that
 # were merged in 59037a57 ("Merge threshold-signatures repo"). Their full
 # pre-merge history would otherwise pollute the changelog.

.github/prompts/pr-review.prompt.md

@@ -56,7 +56,7 @@ REVIEW STYLE:
 - Flag code-comment quality issues per [engineering-standards.md]. The goal is to avoid comments that may become stale or add little value to the reader.
 - Do NOT comment on style, formatting, or naming unless it causes a bug.
 - Do NOT restate what the diff already shows
-- Do NOT ask for `third-party-licenses/licenses.html` to be regenerated on a dependency or lockfile change. Those notices are refreshed during release preparation by [prepare-release.sh]; drift between releases is expected and no CI job gates it. Stale notices are only a finding on a release PR, where that script should already have refreshed them.
+- Do NOT ask for `third-party-licenses/licenses.html` to be regenerated on a dependency or lockfile change. Those notices are refreshed during release preparation by [prepare-github-release.sh]; drift between releases is expected and no CI job gates it. Stale notices are only a finding on a release PR, where that script should already have refreshed them.
 - If no critical issues found: approve with a one-line summary
 - Sign off with: ✅ (approved) or ⚠️ (issues found)
 
@@ -109,4 +109,4 @@ Please always use `gh pr comment` to post your review instead.
 [AGENTS.md]: ../../AGENTS.md
 [CONTRIBUTING.md]: ../../CONTRIBUTING.md
 [engineering-standards.md]: ../../docs/engineering-standards.md
-[prepare-release.sh]: ../../scripts/ops/prepare-release.sh
+[prepare-github-release.sh]: ../../scripts/ops/prepare-github-release.sh

RELEASES.md

@@ -53,19 +53,19 @@ with whatever version you're releasing.
 ### 1. Prepare the release PR
 
 Create a working branch off the release-source branch, then run
-[`scripts/ops/prepare-release.sh`](./scripts/ops/prepare-release.sh) to apply the
+[`scripts/ops/prepare-github-release.sh`](./scripts/ops/prepare-github-release.sh) to apply the
 release boilerplate (changelog, version bump, ABI snapshot, licenses):
 
 ```sh
 # For a minor/major release:
 git checkout main && git pull
 git checkout -b release-prep/v3.11.0
-./scripts/ops/prepare-release.sh 3.11.0
+./scripts/ops/prepare-github-release.sh 3.11.0
 
 # For a patch release:
 git checkout release/v3.11 && git pull
 git checkout -b release-prep/v3.11.1
-./scripts/ops/prepare-release.sh 3.11.1
+./scripts/ops/prepare-github-release.sh 3.11.1
 ```
 
 Push the working branch and open a PR against `main` (for minor releases)
@@ -233,7 +233,7 @@ We follow [Semantic Versioning](https://semver.org/) with these compatibility ru
 ## Changelog conventions
 
 We use [`git-cliff`](https://git-cliff.org/) to maintain `CHANGELOG.md`.
-The `scripts/ops/prepare-release.sh` script invokes `git-cliff -t <VERSION>
+The `scripts/ops/prepare-github-release.sh` script invokes `git-cliff -t <VERSION>
 <BASE_TAG>..<HEAD-SHA>`, where `BASE_TAG` is the most recent **semver**
 tag (`X.Y.Z`) reachable from `HEAD`, found via `git describe` with a
 `--match` glob that skips stray non-semver tags. The range head is a

scripts/ops/prepare-release.sh scripts/ops/prepare-github-release.shscripts/ops/prepare-release.sh renamed to scripts/ops/prepare-github-release.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 #
-# prepare-release.sh — Apply the local file changes for a release.
+# prepare-github-release.sh — Apply the local file changes for a release.
 #
 # Run this on a working branch off the release-source branch (e.g. off
 # `main` for a minor release, off `release/vX.Y` for a patch). The script
@@ -14,8 +14,8 @@
 #   4. Regenerate third-party licenses
 #   5. Commit the release changes
 #
-# Usage:  ./scripts/ops/prepare-release.sh <VERSION>
-# Example: ./scripts/ops/prepare-release.sh 3.6.0
+# Usage:  ./scripts/ops/prepare-github-release.sh <VERSION>
+# Example: ./scripts/ops/prepare-github-release.sh 3.6.0
 #
 
 set -euo pipefail