Predictable URL for release downloads #10562

New Issue

GiteaMirror · 2025-11-02T09:11:21-06:00

GiteaMirror commented

2025-11-02 09:11:21 -06:00

Originally created by @mikhirev on GitHub (Mar 30, 2023).

Feature Description

It would be very helpful if released files had a predictable URL, so that it would be possible to download them without knowing a Gitea internal UUID. It is needed for automation scripts.

E. g. such URL could have a path /<project_path>/releases/tag/<tag_name>/assets/<file_name>.

Screenshots

No response

Originally created by @mikhirev on GitHub (Mar 30, 2023). ### Feature Description It would be very helpful if released files had a predictable URL, so that it would be possible to download them without knowing a Gitea internal UUID. It is needed for automation scripts. E. g. such URL could have a path `/<project_path>/releases/tag/<tag_name>/assets/<file_name>`. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:11:21 -06:00

GiteaMirror closed this issue

2025-11-02 09:11:21 -06:00

GiteaMirror commented

2025-11-02 09:11:21 -06:00

@JakobDev commented on GitHub (Mar 30, 2023):

This should be simple. I see, if I can can do it tomorrow.

@JakobDev commented on GitHub (Mar 30, 2023): This should be simple. I see, if I can can do it tomorrow.

GiteaMirror commented

2025-11-02 09:11:22 -06:00

@jolheiser commented on GitHub (Mar 30, 2023):

Duplicate of https://github.com/go-gitea/gitea/issues/10919

@JakobDev you may want to read the linked issue for context on past discussions, but this would be a great thing to have cleared up. ❤️

@jolheiser commented on GitHub (Mar 30, 2023): Duplicate of https://github.com/go-gitea/gitea/issues/10919 @JakobDev you may want to read the linked issue for context on past discussions, but this would be a great thing to have cleared up. ❤️

GiteaMirror commented

2025-11-02 09:11:22 -06:00

@mikhirev commented on GitHub (Mar 30, 2023):

Well, IIUC the original problem was that multiple releases could have files with the same name attached that lead to collisions. But what I propose is including release tag in path, so cross-release collisions are impossible. I can't imagine why should someone want to have files with identical names in the same release.

@mikhirev commented on GitHub (Mar 30, 2023): Well, IIUC the original problem was that multiple releases could have files with the same name attached that lead to collisions. But what I propose is including release tag in path, so cross-release collisions are impossible. I can't imagine why should someone want to have files with identical names in the same release.

GiteaMirror commented

2025-11-02 09:11:22 -06:00

@JakobDev commented on GitHub (Mar 31, 2023):

I have currently Problems running Gitea, so I can't do this today. Maybe next week.

@JakobDev commented on GitHub (Mar 31, 2023): I have currently Problems running Gitea, so I can't do this today. Maybe next week.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10562