Fixes a race in the Linux+Windows parallel release upload: both jobs GET the release by tag (404 if not yet created), then both POST create — the loser gets 422 with an empty id and its assets never upload.\n\nAdds || true to the create and a fallback re-fetch of the release id by tag when create fails, so both jobs attach their assets even if the other won the creation race.
Fixes a race in the Linux+Windows parallel release upload: both jobs GET the release by tag (404 if not yet created), then both POST create — the loser gets 422 with an empty id and its assets never upload.\n\nAdds `|| true` to the create and a fallback re-fetch of the release id by tag when create fails, so both jobs attach their assets even if the other won the creation race.
Linux and Windows both ensure the release exists in parallel; a job can GET
404 (not yet created) then POST 422 (the other job won the race), leaving its
release id empty so its assets never upload. Add || true to the create and a
fallback re-fetch of the release id by tag when the create fails, so both jobs
upload reliably.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes a race in the Linux+Windows parallel release upload: both jobs GET the release by tag (404 if not yet created), then both POST create — the loser gets 422 with an empty id and its assets never upload.\n\nAdds
|| trueto the create and a fallback re-fetch of the release id by tag when create fails, so both jobs attach their assets even if the other won the creation race.