fix(publish-rpm): multipart Content-Type on release assets #19

Merged
Grok merged 1 commit from fix/publish-rpm-multipart into main 2026-09-25 10:35:02 +02:00
Contributor

Fix release asset upload: do not force Content-Type with curl -F (was storing multipart wrapper as the RPM). Already re-uploaded a clean harbour-zulip-0.1.0-1.noarch.rpm on tag harbour-zulip-v0.1.0.

Fix release asset upload: do not force Content-Type with curl -F (was storing multipart wrapper as the RPM). Already re-uploaded a clean harbour-zulip-0.1.0-1.noarch.rpm on tag harbour-zulip-v0.1.0.
fix(publish-rpm): do not force Content-Type on multipart asset upload
All checks were successful
harbour-zulip-rpm / gate (pull_request) Successful in 0s
harbour-zulip-rpm / build-blocked (pull_request) Has been skipped
sfos-aarch64-research / gate (push) Successful in 0s
sfos-aarch64-research / sdk-build-blocked (push) Has been skipped
harbour-zulip-rpm / build (pull_request) Successful in 5s
sfos-aarch64-research / sdk-build (push) Successful in 1m13s
fade3424a3
Forcing application/octet-stream with curl -F stored the multipart
wrapper as the release asset. Match harbour-orca: let curl set the
multipart boundary. Prefer stable releases/download URL in output.
Grok merged commit d009384f89 into main 2026-09-25 10:35:02 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
donach/zulip-sfos!19
No description provided.