diff --git a/bin/release.sh b/bin/release.sh
index 48177da63..905afdea4 100755
--- a/bin/release.sh
+++ b/bin/release.sh
@@ -274,7 +274,7 @@ print_publish_instructions() {
     echo
     print_status "${prefix}Next: trigger the Buildkite publish build."
     echo
-    echo "  1. Open https://buildkite.com/automattic/gutenbergkit/builds/new"
+    echo "  1. Open https://buildkite.com/organizations/automattic/pipelines/gutenbergkit/builds/new"
     echo "  2. Branch: trunk"
     echo "  3. Commit: $sha"
     echo "  4. Environment Variables: NEW_VERSION=$tag"
diff --git a/docs/releases.md b/docs/releases.md
index fb9ecaee2..63e3aa92a 100644
--- a/docs/releases.md
+++ b/docs/releases.md
@@ -53,7 +53,7 @@ It does **not** create the git tag or the GitHub release — that's Step 2.
 
 Step 1 prints the SHA of the version-bump commit it just pushed. Trigger a new Buildkite build with that SHA pinned:
 
-1. Open <https://buildkite.com/automattic/gutenbergkit/builds/new>
+1. Open <https://buildkite.com/organizations/automattic/pipelines/gutenbergkit/builds/new>
 2. **Branch**: `trunk`
 3. **Commit**: the SHA printed by Step 1
 4. **Environment Variables**: `NEW_VERSION=vX.Y.Z`