After adding a new tag in release page, I can't find it in tag list. #14717

New Issue

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

GiteaMirror commented

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

Originally created by @why0why0why on GitHub (Jul 7, 2025).

Description

A user reported creating a new tag on the release page but couldn't find it listed in the tags section.

I tried pulling the tag locally from the remote repository and succeeded. I could also see the new tag appearing in the timeline feed and on the commit page.

I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere.

After deleting the tag again, I noticed it still appeared on the commit page! Clicking it just returned a 404 error.

Eventually, I found the tag buried on the last page of the tag list – even though it was newly created and should have been on the first page.

The fix: After upgrading Gitea from 1.23.7 to 1.24.2, I deleted the tag on tag list page, then recreated it. This time everything worked correctly – the release appeared as expected.

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.45.1.windows.1

Operating System

windows 10 22H2

How are you running Gitea?

Downloaded from github release and ran the exe file

Database

None

Originally created by @why0why0why on GitHub (Jul 7, 2025). ### Description A user reported creating a new tag on the release page but couldn't find it listed in the tags section. I tried pulling the tag locally from the remote repository and succeeded. I could also see the new tag appearing in the timeline feed and on the commit page. I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere. After deleting the tag again, I noticed it still appeared on the commit page! Clicking it just returned a 404 error. Eventually, I found the tag buried on the last page of the tag list – even though it was newly created and should have been on the first page. The fix: After upgrading Gitea from 1.23.7 to 1.24.2, I deleted the tag on tag list page, then recreated it. This time everything worked correctly – the release appeared as expected. ### Gitea Version 1.23.7 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.45.1.windows.1 ### Operating System windows 10 22H2 ### How are you running Gitea? Downloaded from github release and ran the exe file ### Database None

GiteaMirror added the type/bug issue/needs-feedback labels 2025-11-02 11:21:00 -06:00

GiteaMirror closed this issue

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

GiteaMirror commented

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

@wxiaoguang commented on GitHub (Jul 7, 2025):

The fix: After upgrading Gitea from 1.23.7 to 1.24.2, I deleted the tag on tag list page, then recreated it. This time everything worked correctly – the release appeared as expected.

1.23 is an old and outdated release , 1.24 is the stable and maintained one.

So if 1.24 doesn't have the bug, then it should be fine.

@wxiaoguang commented on GitHub (Jul 7, 2025): > The fix: After upgrading Gitea from 1.23.7 to 1.24.2, I deleted the tag on tag list page, then recreated it. This time everything worked correctly – the release appeared as expected. 1.23 is an old and outdated release , 1.24 is the stable and maintained one. So if 1.24 doesn't have the bug, then it should be fine.

GiteaMirror commented

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

@why0why0why commented on GitHub (Jul 9, 2025):

1.23 is an old and outdated release , 1.24 is the stable and maintained one.

So if 1.24 doesn't have the bug, then it should be fine.

Today, even after I'd upgraded Gitea, he created a new tag on the release page and the bug resurfaced.

We've found that creating a new tag locally and pushing it to the remote works correctly; however, creating the tag directly on the release page causes the issue.

@why0why0why commented on GitHub (Jul 9, 2025): > 1.23 is an old and outdated release , 1.24 is the stable and maintained one. > > So if 1.24 doesn't have the bug, then it should be fine. Today, even after I'd upgraded Gitea, he created a new tag on the release page and the bug resurfaced. We've found that creating a new tag locally and pushing it to the remote works correctly; however, creating the tag directly on the release page causes the issue.

GiteaMirror commented

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

@wxiaoguang commented on GitHub (Jul 9, 2025):

Please provide detailed reproducible steps. For example: first click this, then input that, then click xxx, then expect to see, but ....

And please try to reproduce on https://demo.gitea.com/

@wxiaoguang commented on GitHub (Jul 9, 2025): Please provide detailed reproducible steps. For example: first click this, then input that, then click xxx, then expect to see, but .... And please try to reproduce on https://demo.gitea.com/

GiteaMirror commented

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

@wxiaoguang commented on GitHub (Jul 9, 2025):

I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere.

Are you sure you created a "release" but not a "draft"? Please provide the detailed reproducible steps if there is any problem.

@wxiaoguang commented on GitHub (Jul 9, 2025): > I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere. Are you sure you created a "release" but not a "draft"? Please provide the detailed reproducible steps if there is any problem.

GiteaMirror commented

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

@why0why0why commented on GitHub (Jul 9, 2025):

Please provide detailed reproducible steps. For example: first click this, then input that, then click xxx, then expect to see, but ....

And please try to reproduce on https://demo.gitea.com/

First open the repo page, then click releases, new release, input tag name, and then press create tag only.

I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere.

Are you sure you created a "release" but not a "draft"? Please provide the detailed reproducible steps if there is any problem.

So I just create a new tag without release. It's not a release, and not a draft either. If it works correctly, a new release will be created by CI, which contains a step to create release by gitea API.

@why0why0why commented on GitHub (Jul 9, 2025): > Please provide detailed reproducible steps. For example: first click this, then input that, then click xxx, then expect to see, but .... > > And please try to reproduce on https://demo.gitea.com/ First open the repo page, then click `releases`, `new release`, input tag name, and then press `create tag only`. > > I then deleted the tag remotely, recreated it, and pushed again. The CI ran successfully, confirming it had created a new release. However, the release itself wasn't visible anywhere. > > Are you sure you created a "release" but not a "draft"? Please provide the detailed reproducible steps if there is any problem. So I just create a new tag without release. It's not a release, and not a draft either. If it works correctly, a new release will be created by CI, which contains a step to create release by gitea API.

GiteaMirror commented

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

@wxiaoguang commented on GitHub (Jul 9, 2025):

Unable to reproduce:

@wxiaoguang commented on GitHub (Jul 9, 2025): Unable to reproduce: <img width="1774" height="1362" alt="Image" src="https://github.com/user-attachments/assets/cba47180-503e-46f3-9b86-e2cd431911e8" /> <img width="1848" height="954" alt="Image" src="https://github.com/user-attachments/assets/ff1920b5-bb61-4311-907d-f351bf89a869" />

GiteaMirror commented

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

@GiteaBot commented on GitHub (Aug 8, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Aug 8, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:

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#14717