Tags not visible after upgrade to 1.20.5 #12006

New Issue

GiteaMirror · 2025-11-02T09:54:17-06:00

GiteaMirror commented

2025-11-02 09:54:17 -06:00

Originally created by @dawnstrider on GitHub (Nov 14, 2023).

Description

I am trying to migrate from GOGS to GITEA. I have successfully taken all data, migrated to 1.0.2, then upgraded all the way to 1.19.4. I did "doctor recreate-table" with 1.19.4 to fix the table issues from previous versions.

Now, when I upgrade to 1.20.5, my repos loose all their tags in the UI. They are still there when i do a checkout, but not visible in the UI anymore.

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Self-hosted on Ubuntu with the binary file.

Database

None

Originally created by @dawnstrider on GitHub (Nov 14, 2023). ### Description I am trying to migrate from GOGS to GITEA. I have successfully taken all data, migrated to 1.0.2, then upgraded all the way to 1.19.4. I did "doctor recreate-table" with 1.19.4 to fix the table issues from previous versions. Now, when I upgrade to 1.20.5, my repos loose all their tags in the UI. They are still there when i do a checkout, but not visible in the UI anymore. ### Gitea Version 1.20.5 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Self-hosted on Ubuntu with the binary file. ### Database None

GiteaMirror added the type/bug issue/workaround labels 2025-11-02 09:54:17 -06:00

GiteaMirror closed this issue

2025-11-02 09:54:17 -06:00

GiteaMirror commented

2025-11-02 09:54:18 -06:00

@JakobDev commented on GitHub (Nov 14, 2023):

The tags are read from the database. Have you tried to push with the tags to the repo, to maybe trigger Gitea to add the branches to the database? I think this should also be added to the Admin dashboard.

@JakobDev commented on GitHub (Nov 14, 2023): The tags are read from the database. Have you tried to push with the tags to the repo, to maybe trigger Gitea to add the branches to the database? I think this should also be added to the Admin dashboard.

GiteaMirror commented

2025-11-02 09:54:18 -06:00

@dawnstrider commented on GitHub (Nov 14, 2023):

Thanks for the hint. I found a solution with your remark:

To populate the "releases" table, which seems to be used for the tags since 1.20.x, I need to run "gitea-.... admin repo-sync-releases" which will put all tags into the releases table.

Afterwards, the tag list is updated again on the UI.

@dawnstrider commented on GitHub (Nov 14, 2023): Thanks for the hint. I found a solution with your remark: To populate the "releases" table, which seems to be used for the tags since 1.20.x, I need to run "_gitea-.... admin repo-sync-releases_" which will put all tags into the releases table. Afterwards, the tag list is updated again on the UI.

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