docs: fix stale sprout repo references in RELEASING.md (#1043)

Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
Co-authored-by: npub16v54tttfqacx9ycvc3k0ut0npj564ahcuajzy6qjvh57ntmsf4uq4806j2 <d32955ad69077062930cc46cfe2df30ca9aaf6f8e76422681265e9e9af704d78@sprout-oss.stage.blox.sqprod.co>
This commit is contained in:
Will Pfleger
2026-06-14 12:23:53 -04:00
committed by GitHub
parent d02aee2021
commit b2ad3074ba

View File

@@ -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<version>` 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: