Commit ee5f1b0
fix(ci): stop the release upload racing itself on overlapping globs
The `files:` list matched nine assets twice. `artifacts/openshrimp-*`
already covers the security-key helper, the HCS initrd, both rootfs
images and the RDP helper, and each of those carried its own explicit
line as well. A file listed twice is uploaded twice concurrently, and
the second upload deletes the asset the first just created, so the step
dies on a bare "Not Found" against delete-a-release-asset with no
indication of which file or why.
The duplication has been there for several releases and was survivable
by luck: the action tolerates most of the resulting metadata races with
"Matching asset is present after refresh; continuing...". v0.36.0 added
a 26th asset, shifted the timing, and lost — twice, the second time
worse, because a re-run finds the draft already populated and must
delete-then-replace every asset rather than merely upload it.
That the overlap is the cause rather than a coincidence is legible in
the first attempt's log: all eight metadata warnings name one of the
nine duplicated assets, and no asset outside that set produced one.
Dropping the five redundant patterns leaves all 26 assets covered, none
of them twice. Verified by matching the pattern list against the real
asset names rather than by reading it.
Co-Authored-By: Claude <noreply@anthropic.com>1 parent 83023a8 commit ee5f1b0
1 file changed
Lines changed: 6 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
915 | 915 | | |
916 | 916 | | |
917 | 917 | | |
| 918 | + | |
| 919 | + | |
| 920 | + | |
| 921 | + | |
| 922 | + | |
| 923 | + | |
918 | 924 | | |
919 | 925 | | |
920 | 926 | | |
921 | | - | |
922 | | - | |
923 | | - | |
924 | | - | |
925 | | - | |
926 | 927 | | |
927 | 928 | | |
928 | 929 | | |
0 commit comments