Publishing a Draft Release doesn't show up in user's activity #6754

Open
opened 2025-11-02 07:05:37 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @fnetX on GitHub (Jan 25, 2021).

Description

When releases were first saved as a draft and released later, they won't show up in the public activity or the personal dashboard of a user.

Additionally, draft releases result in a 404 not found, see https://try.gitea.io/fnetx/testing-gitea-releases/releases/tag/r3
I think it'd be better to either display draft releases as well or prevent them from being clicked. It's somewhat confusing 🙃

Screenshots

Screenshot of the public activity timeline of Gitea which only displays the release for the first published one, not for the second which was saved as a draft first.
Sorry this screenshot is in German. The UI translation feels a bit strange actually, will dive into this another time.
But you can see that the second release doesn't show up. Only the first one which was published directly without saving it as a Draft.

Originally created by @fnetX on GitHub (Jan 25, 2021). - Gitea version (or commit ref): 1.14.0+dev-605-gd2ea21d0 - Can you reproduce the bug at https://try.gitea.io: - [X] Yes https://try.gitea.io/fnetx?tab=activity and https://try.gitea.io/fnetx/testing-gitea-releases/releases ## Description When releases were first saved as a draft and released later, they won't show up in the public activity or the personal dashboard of a user. Additionally, draft releases result in a 404 not found, see https://try.gitea.io/fnetx/testing-gitea-releases/releases/tag/r3 I think it'd be better to either display draft releases as well or prevent them from being clicked. It's somewhat confusing :upside_down_face: ## Screenshots ![Screenshot of the public activity timeline of Gitea which only displays the release for the first published one, not for the second which was saved as a draft first.](https://user-images.githubusercontent.com/19634137/105768623-ee070700-5f5c-11eb-8dcd-cf75fc653694.png) Sorry this screenshot is in German. The UI translation feels a bit strange actually, will dive into this another time. But you can see that the second release doesn't show up. Only the first one which was published directly without saving it as a Draft.
GiteaMirror added the issue/not-a-bug label 2025-11-02 07:05:37 -06:00
Author
Owner

@lunny commented on GitHub (Jan 26, 2021):

I think a draft means we haven't finished the release. I don't think we should publish an activity for that.

@lunny commented on GitHub (Jan 26, 2021): I think a draft means we haven't finished the release. I don't think we should publish an activity for that.
Author
Owner

@fnetX commented on GitHub (Jan 26, 2021):

The point is, that the release won't show up, when you finally release the draft. A release should always show up, no matter if the state was once a Draft.

@fnetX commented on GitHub (Jan 26, 2021): The point is, that the release won't show up, when you finally release the draft. A release should always show up, no matter if the state was once a Draft.
Author
Owner

@lunny commented on GitHub (Mar 27, 2024):

I think a draft means we haven't finished the release. I don't think we should publish an activity for that.

The behavior is following Github. A draft of the release can only be visited by users who have write permission to release until it's published. It's convenient for maintainers to do some preparation before it publishes.

@lunny commented on GitHub (Mar 27, 2024): > I think a draft means we haven't finished the release. I don't think we should publish an activity for that. The behavior is following Github. A draft of the release can only be visited by users who have write permission to release until it's published. It's convenient for maintainers to do some preparation before it publishes.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6754