Incorrect latest release shown after mirroring GitHub repository to Gitea #14864

New Issue

2025-11-02T11:24:41-06:00

GiteaMirror commented

2025-11-02 11:24:41 -06:00

Originally created by @TrevorBenson on GitHub (Aug 13, 2025).

Description

When mirroring an existing repository from GitHub the Latest release in Gitea does not match the latest release in GitHub.

I mirrored a repository which has releases v1.4.6, v1.4.7-pre and v1.4.7.

In GitHub:

On the main page Releases sidebar shows v1.4.7 is Latest.
On the releases page:
- v1.4.6 is at the top of the list with no label.
- v1.4.7 below it with the Latest label.
- v1.4.7-pre below v1.4.7 with the Pre-release label.

In Gitea:

On the main page Releases sidebar shows v1.4.6 is Latest.
On the releases page:
- v1.4.6 is at the top of the list with a Stable label.
- v1.4.7-pre below it with the Pre-release label.
- v1.4.7 below v1.4.7-pre with the Stable label.

Gitea Version

1.24.4

Can you reproduce the bug on the Gitea demo site?

No. I will attempt reproducing the issue on the demo Gitea site with a public repository when I get a chance.

TL;DR

The mirror is of one of my personal/private repositories from GitHub. I was hoping to find one with similar oddity on the releases sort order first, but so far each public repo I look at has latest as the top release so I don't have an example yet of a release that is older by version/tag AND date at the top of the page with a newer version/tag/date lower in the list. If I don't find one I will just attempt to reproduce with any public repo that has releases.

Log Gist

No response

Screenshots

No response

Git Version

2.39.5

Operating System

Debian GNU/Linux 12 (bookworm)

How are you running Gitea?

Gitea LXC container container deployed on proxmox server. Manually upgraded to 1.24.4 via:

Downloading the binary via url https://dl.gitea.com/gitea/1.24.4/gitea-1.24.4-linux-amd64
Making it executable
Replacing the existing binary used by the gitea.service
Restarting the service.

Database

MySQL/MariaDB

Originally created by @TrevorBenson on GitHub (Aug 13, 2025). ### Description When mirroring an existing repository from GitHub the Latest release in Gitea does not match the latest release in GitHub. I mirrored a repository which has releases v1.4.6, v1.4.7-pre and v1.4.7. ## In GitHub: - On the main page Releases sidebar shows v1.4.7 is Latest. - On the releases page: - v1.4.6 is at the top of the list with no label. - v1.4.7 below it with the **Latest** label. - v1.4.7-pre below v1.4.7 with the **Pre-release** label. ## In Gitea: - On the main page Releases sidebar shows v1.4.6 is Latest. - On the releases page: - v1.4.6 is at the top of the list with a **Stable** label. - v1.4.7-pre below it with the **Pre-release** label. - v1.4.7 below v1.4.7-pre with the **Stable** label. ### Gitea Version 1.24.4 ### Can you reproduce the bug on the Gitea demo site? No. I will attempt reproducing the issue on the demo Gitea site with a public repository when I get a chance. #### TL;DR The mirror is of one of my personal/private repositories from GitHub. I was hoping to find one with similar oddity on the releases sort order first, but so far each public repo I look at has latest as the top release so I don't have an example yet of a release that is older by version/tag AND date at the top of the page with a newer version/tag/date lower in the list. If I don't find one I will just attempt to reproduce with any public repo that has releases. ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.39.5 ### Operating System Debian GNU/Linux 12 (bookworm) ### How are you running Gitea? Gitea LXC container container deployed on proxmox server. Manually upgraded to 1.24.4 via: 1. Downloading the binary via url https://dl.gitea.com/gitea/1.24.4/gitea-1.24.4-linux-amd64 2. Making it executable 3. Replacing the existing binary used by the gitea.service 4. Restarting the service. ### Database MySQL/MariaDB

GiteaMirror added the type/bug label 2025-11-02 11:24:42 -06:00

GiteaMirror commented

2025-11-02 11:24:42 -06:00

@codemonky commented on GitHub (Aug 25, 2025):

Having the same issue. I was able to reproduce the issue on the Gitea demo site. Tags are not ordered the same way they are on GitHub

@codemonky commented on GitHub (Aug 25, 2025): Having the same issue. I was able to reproduce the issue on the Gitea demo site. Tags are not ordered the same way they are on GitHub

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