API: POST releases/{id}/assets should accept application/octet-stream #12563

Closed
opened 2025-11-02 10:14:11 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @silverwind on GitHub (Feb 29, 2024).

Originally assigned to: @KN4CK3R on GitHub.

Feature Description

Adding release assets on GitHub's API accepts application/octet-stream while Gitea's API accepts multipart/form-data.

It should be made to accept both which is necessary for actions like ncipollo/release-action to work.

Originally created by @silverwind on GitHub (Feb 29, 2024). Originally assigned to: @KN4CK3R on GitHub. ### Feature Description Adding release assets on GitHub's API [accepts `application/octet-stream`](https://docs.github.com/en/rest/releases/assets?apiVersion=2022-11-28#upload-a-release-asset) while Gitea's API [accepts `multipart/form-data`](https://github.com/go-gitea/gitea/blob/c7dcb58b1d96970959a5c8ac8d3955e4b7d027df/routers/api/v1/repo/release_attachment.go#L155-L156). It should be made to accept both which is necessary for actions like [`ncipollo/release-action`](https://github.com/ncipollo/release-action) to work.
GiteaMirror added the topic/gitea-actionstopic/api labels 2025-11-02 10:14:11 -06:00
Author
Owner

@KN4CK3R commented on GitHub (Feb 29, 2024):

Strange that this essential endpoint is not Github compatible.

@KN4CK3R commented on GitHub (Feb 29, 2024): Strange that this essential endpoint is not Github compatible.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12563