Docker Hub `latest` Tag Points to Release Candidate 1.18.0-rc0

[julmb]

Description

Currently, the latest tag for gitea on docker hub [1] points to the same image as the 1.18.0-rc0 tag [2]. The documentation says that the latest tag should only point to stable releases.

This has happened before with 1.17.0 (#20058) and the configuration was apparently changed to prevent it from happening again, but now it has happened again.

[1] https://hub.docker.com/layers/gitea/gitea/latest/images/sha256-167f91cbf8f2d8e031d22c57928a157d4772aa378baa116a2f71f703b70b367f
[2] https://hub.docker.com/layers/gitea/gitea/1.18.0-rc0/images/sha256-167f91cbf8f2d8e031d22c57928a157d4772aa378baa116a2f71f703b70b367f

Gitea Version

1.18.0-rc0

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?

Gitea from Docker Hub run via Docker Compose

Database

No response

[6543]

ref https://gitea.com/gitea/drone-docker/pulls/2

[lunny]

Since it has been tagged, I would like to stay latest == 1.18rc0, if we delete the tag, some users will encounter a downgrade. Our task is to push the 1.18.0 releasing ASAP.

[6543]

same game as last time 😓

[MrHaroldA]

Since it has been tagged, I would like to stay latest == 1.18rc0, if we delete the tag, some users will encounter a downgrade.

I actually encountered this, but a downgrade to 1.17 fails to start after an update to 1.18rc0, so I just went with 1.18rc0 after reading that it should be near a real release.

[ricariel]

I would love to see a stable tag for this.

[xPuls3]

As the documentation says 'latest' is stable, it threw me off to see a release candidate version installed.
I would definitely like a 'stable' tag as mentioned above if this is going to continue happening.

[lunny]

As the documentation says 'latest' is stable, it threw me off to see a release candidate version installed. I would definitely like a 'stable' tag as mentioned above if this is going to continue happening.

Sorry, that's an accident event.

[f0086]

So, over a month later, the latest tag is still on the .rc1.
The 1.18.0 milestone seems almost complete for some time (https://github.com/go-gitea/gitea/milestone/120), when are you planning to push the 1.8.0 release?

[lunny]

So, over a month later, the latest tag is still on the .rc1. The 1.18.0 milestone seems almost complete for some time (https://github.com/go-gitea/gitea/milestone/120), when are you planning to push the 1.8.0 release?

It should be soon and we fixed many bugs these days.

[notDavid]

So does this mean everyone on the latest tag (= 1.18.0+rc1) now doesn't have security fixes of 1.17.4 ?

https://github.com/go-gitea/gitea/releases/tag/v1.17.4

[zeripath]

I think we do need to do another RC of 1.18 or release it. I'm not sure if we feel it's ready yet for release but it's getting there.