[DOCKER] Installing with ":latest" tag will install a RC #10990

Closed
opened 2025-11-02 09:24:14 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @realizelol on GitHub (Jun 8, 2023).

Description

I'm using gitea/gitea:latest which should install the latest stable version, as mentioned in the docs Install-With-Docker:

For a stable release you can use :latest, :1 or specify a certain release like :main-nightly, but if you'd like to use the latest development version of Gitea then you could use the :dev tag.

On Github it's marked as "pre-release": https://github.com/go-gitea/gitea/releases

Running it with :1 tag will use the correct stable 1.19.3 but cannot really go back to it in case my database is updated.

Gitea Version

1.20.0-rc0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

git version 2.39.2

Operating System

Docker

How are you running Gitea?

Docker with "gitea/gitea:latest" tag.

Database

MySQL

Originally created by @realizelol on GitHub (Jun 8, 2023). ### Description I'm using `gitea/gitea:latest` which should install the latest stable version, as mentioned in the docs [Install-With-Docker](https://docs.gitea.com/next/installation/install-with-docker): _For a stable release you can use **:latest**, **:1** or specify a certain release like **:main-nightly**, but if you'd like to use the latest development version of Gitea then you could use the **:dev** tag._ On Github it's marked as "pre-release": https://github.com/go-gitea/gitea/releases Running it with **:1** tag will use the correct stable `1.19.3` but cannot really go back to it in case my database is updated. ### Gitea Version 1.20.0-rc0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version git version 2.39.2 ### Operating System Docker ### How are you running Gitea? Docker with "gitea/gitea:latest" tag. ### Database MySQL
GiteaMirror added the type/bugtopic/build labels 2025-11-02 09:24:14 -06:00
Author
Owner

@jrjake commented on GitHub (Jun 8, 2023):

Seems like #21615 wasn't truly fixed

@jrjake commented on GitHub (Jun 8, 2023): Seems like #21615 wasn't truly fixed
Author
Owner

@lunny commented on GitHub (Jun 8, 2023):

There is a regression imo.

@lunny commented on GitHub (Jun 8, 2023): There is a regression imo.
Author
Owner

@notDavid commented on GitHub (Jun 8, 2023):

I can confirm... i have the same issue (as #21615 ) again.

@notDavid commented on GitHub (Jun 8, 2023): I can confirm... i have the same issue (as #21615 ) again.
Author
Owner

@delvh commented on GitHub (Jun 8, 2023):

I know, I wasn't fast enough with cancelling the release pipeline for the v1.21.0-dev tag.
That's why a Docker image was pushed.

@delvh commented on GitHub (Jun 8, 2023): I know, I wasn't fast enough with cancelling the release pipeline for the `v1.21.0-dev` tag. That's why a Docker image was pushed.
Author
Owner

@lunny commented on GitHub (Jul 27, 2023):

Since v1.20.1 is released, this has been corrected.

@lunny commented on GitHub (Jul 27, 2023): Since v1.20.1 is released, this has been corrected.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10990