Use local Bazel for voice release builds (#58727)

## Why

BuildBuddy credentials are unavailable for voice release builds.

## What changed

Set `BUILDBUDDY_API_KEY` to an empty string in the Linux, macOS, and Windows voice release build steps so the Bazel wrappers use their local configuration.

GitOrigin-RevId: 69e47d6b6077fbb74b5895eacbe587766345b7ec
This commit is contained in:
Felipe Coury
2026-11-01 16:44:41 +00:00
committed by copyberry
parent 54201ea65a
commit 4b4a5cf25a
2 changed files with 6 additions and 3 deletions
+4 -2
View File
@@ -326,7 +326,8 @@ jobs:
shell: bash
env:
APP_TARGET: ${{ matrix.target }}
BUILDBUDDY_API_KEY: ${{ secrets.BUILDBUDDY_API_KEY }}
# Use local Bazel while BuildBuddy credentials are unavailable.
BUILDBUDDY_API_KEY: ""
run: |
set -euo pipefail
cd "$GITHUB_WORKSPACE"
@@ -605,7 +606,8 @@ jobs:
env:
TARGET: ${{ matrix.target }}
PREFIX: ${{ matrix.prefix }}
BUILDBUDDY_API_KEY: ${{ secrets.BUILDBUDDY_API_KEY }}
# Use local Bazel while BuildBuddy credentials are unavailable.
BUILDBUDDY_API_KEY: ""
run: |
set -euo pipefail
# Release tags bump Cargo.toml without rewriting the workspace lockfile.