Skip to content

ci: migrate to goreleaser Gen 2 (PLA-452)#16

Merged
linuskendall merged 1 commit into
masterfrom
pla-452-shredstream-proxy-migrate-to-goreleaser-gen-2
May 5, 2026
Merged

ci: migrate to goreleaser Gen 2 (PLA-452)#16
linuskendall merged 1 commit into
masterfrom
pla-452-shredstream-proxy-migrate-to-goreleaser-gen-2

Conversation

@linuskendall

Copy link
Copy Markdown
Member

Summary

  • Add .goreleaser.yaml building jito-shredstream-proxy for linux/amd64 with artifact name jito-shredstream-proxy-linux-amd64
  • Add .github/workflows/goreleaser-config-check.yaml for PR-time validation of the goreleaser config
  • GCS upload, cosigning, and GitHub Release publishing are injected via ci/goreleaser-patch.yaml in Binaries-ci at build time
  • Builds are triggered manually via build-release.yml in Binaries-ci (public repo — no auto-trigger on tag)

Part of PLA-412 / PLA-452: migrating shredstream-proxy to Binaries-ci Gen 2 goreleaser workflow.

Test plan

  • Verify goreleaser check passes in the config check workflow
  • Trigger a manual build via gh workflow run build-release.yml --repo rpcpool/Binaries-ci --field org=rpcpool --field repo=shredstream-proxy --field tag=<tag>
  • Confirm artifact jito-shredstream-proxy-linux-amd64 is uploaded to nomad-triton-test/shredstream-proxy/v<semver>/

🤖 Generated with Claude Code

Add .goreleaser.yaml building jito-shredstream-proxy for linux/amd64
with artifact name jito-shredstream-proxy-linux-amd64. Add goreleaser
config check workflow for PR validation. GCS upload and cosigning are
injected by ci/goreleaser-patch.yaml in Binaries-ci at build time.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@linuskendall linuskendall merged commit 20b2799 into master May 5, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants