chore(ci): use http delete instead of curl DELETE #37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/use-http-delete"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Replace the best-effort
curl --request DELETEcalls in the Generic Package publish steps (binary +.sha256sidecar) with Nushell's nativehttp delete --full --allow-errors. The new form checks the response status: 204 (deleted) and 404 (nothing to delete) are tolerated, anything else aborts the workflow with a clear message. This surfaces real registry-side errors (auth failure, rate limiting, etc.) that the curl form silently swallowed because there was no--failflag and no exit-code check. Applied to bothbuild-linux.ymlandbuild-windows.yml.Test plan
build-linux.ymlandbuild-windows.ymlshould still see "DELETE returned 204" (or 404 on the very first publish of a new tag) for both the binary and the sidecar, and the subsequent PUTs should succeed.