Skip to content

Commit 07a08b3

Browse files
Your Nameclaude
andcommitted
fix(release): only download calm-* artifacts in the release job
The bare download-artifact step grabs every artifact in the run, including the *.dockerbuild build-record docker/build-push-action v6 uploads when the parallel docker job finishes first — and downloading that artifact fails hard after 5 retries, killing the release job. That race is how the v0.3.2 release attempt died twice; v0.3.1 only passed because docker finished after release. Filter to the binary tarballs, which is all this job ever needed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 443a25a commit 07a08b3

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

.github/workflows/release.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -123,6 +123,15 @@ jobs:
123123
with:
124124
path: dist
125125
merge-multiple: true
126+
# Only the binary tarballs from the build matrix. Without this
127+
# filter, "download all" also grabs the `*.dockerbuild` build-record
128+
# artifact docker/build-push-action v6 uploads whenever the `docker`
129+
# job happens to finish before this one — and downloading that
130+
# artifact fails hard (5 retries, then kills the job), which is
131+
# exactly how the first v0.3.2 release attempt died. `needs: build`
132+
# only orders this job after the build matrix; `docker` runs in
133+
# parallel, so whether it sneaks its artifact in first is a race.
134+
pattern: "calm-*"
126135

127136
- name: Generate checksums
128137
working-directory: dist

0 commit comments

Comments
 (0)