Skip to content

ci(release): Split Binary Builds By Artifact#3013

Draft
refcell wants to merge 1 commit into
mainfrom
rf/fix/split-release-binary-builds
Draft

ci(release): Split Binary Builds By Artifact#3013
refcell wants to merge 1 commit into
mainfrom
rf/fix/split-release-binary-builds

Conversation

@refcell
Copy link
Copy Markdown
Contributor

@refcell refcell commented May 28, 2026

Summary

The failing Create RC run lost communication with the hosted ubuntu-24.04-arm runner during the native binary build. Instead of throttling cargo parallelism, this splits the release binary build matrix by artifact.

build-binaries now runs one (target, binary) job for each release artifact, so the four binaries for each target can build independently and in parallel. Each job still packages, checksums, signs, attests, and uploads the same asset names expected by baseup:

  • <binary>-<tag>-<target>.tar.gz
  • <binary>-<tag>-<target>.tar.gz.sha256
  • <binary>-<tag>-<target>.tar.gz.asc

The final publish job still downloads binaries-* with merge-multiple: true and uploads all release assets to GitHub.

Validation

  • go run github.com/rhysd/actionlint/cmd/[email protected] .github/workflows/build-release.yml .github/workflows/create-rc.yml .github/workflows/publish-release.yml
  • git diff --check

@cb-heimdall
Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

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