From ca5f4969226b2d19235b4750b35b1d48b9e428fb Mon Sep 17 00:00:00 2001 From: npub16v54tttfqacx9ycvc3k0ut0npj564ahcuajzy6qjvh57ntmsf4uq4806j2 Date: Sun, 14 Jun 2026 12:22:19 -0400 Subject: [PATCH] docs: fix stale sprout repo references in RELEASING.md The block/sprout -> block/buzz and squareup/sprout-releases -> squareup/buzz-releases renames left two dead links in the release runbook. The Buildkite pipeline slug remains sprout-releases (not yet renamed Buildkite-side), so its URL is intentionally left unchanged. Co-authored-by: Will Pfleger Signed-off-by: Will Pfleger --- RELEASING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 015094dd2c..88f95aa133 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -72,7 +72,7 @@ If the automated flow isn't suitable (e.g., building from a non-main ref): After the OSS release ships, trigger an internal build via the [sprout-releases Buildkite pipeline](https://buildkite.com/runway/sprout-releases). -See the [sprout-releases README](https://github.com/squareup/sprout-releases#cutting-a-release) +See the [buzz-releases README](https://github.com/squareup/buzz-releases#cutting-a-release) for the full step-by-step instructions and input field reference. --- @@ -102,7 +102,7 @@ the same `v` release. Intel users download the `_x64.dmg`. ## Prerequisites -- **Write access** to the `block/sprout` GitHub repository +- **Write access** to the `block/buzz` GitHub repository - **`gh` CLI** authenticated (`gh auth status`) - The following **GitHub Actions secrets** must be configured: