From cc9db6428941dcc88cde62671d18d18c2fda2339 Mon Sep 17 00:00:00 2001 From: linuskendall Date: Tue, 2 Jun 2026 08:27:26 +0000 Subject: [PATCH] ci(goreleaser): pin project_name to shredstream-proxy So the GCS blob directory injected by Binaries-ci's goreleaser-patch ({{ .ProjectName }}/v{{ .Version }}) is always shredstream-proxy/ regardless of build context. When build-release.yml fetches this config to rebuild an older tag that predates the file (e.g. v0.2.12-triton-0004), goreleaser otherwise resolves the project name to the CI repo (Binaries-ci), corrupting the upload path. Co-Authored-By: Claude Opus 4.8 --- .goreleaser.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.goreleaser.yaml b/.goreleaser.yaml index 63070a7f..ace8db12 100644 --- a/.goreleaser.yaml +++ b/.goreleaser.yaml @@ -8,6 +8,13 @@ version: 2 +# Pinned so the GCS blob directory injected by Binaries-ci's +# ci/goreleaser-patch.yaml ({{ .ProjectName }}/v{{ .Version }}) is always +# shredstream-proxy/, independent of the build context. Without this, +# build-release.yml resolves the project name to the CI repo (Binaries-ci) +# when this config is fetched to build an older tag that predates this file. +project_name: shredstream-proxy + builds: - id: jito-shredstream-proxy builder: rust