latest tag being bind to the wrong Docker image

[WarningImHack3r]

Description

The latest tag of your Docker image is often bind to the wrong Gitea version. I often notice that it's bind to some RC version, dev version, or currently to the 1.21.0-dev version, which is definitely not good.

I notice it because I'm running Watchtower daily to always keep my containers up-to-date, and right now my Gitea container has been bumped to this dev version and is no longer working because of an undocumented breaking change.

I can also think about the people attempting to casually download and run Gitea for the first time with a simple gitea/gitea and won't understand why it's not working.

So can you please make sure the :latest tag always points to the latest stable version please?

Gitea Version

1.21.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Git Version

No response

Operating System

Raspberry Pi OS 64bit

How are you running Gitea?

:latest Docker image

Database

SQLite

[lakoliu]

I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now.

[WarningImHack3r]

@lakoliu it's even more a pain that we not only have to manually downgrade but we also have to tweak/disable Watchtower temporarily because it's will bump Gitea again during its next run...

[delvh]

Yes, we know.
We've noticed this bug immediately when releasing 1.20.0-rc0 as the new container was pushed almost immediately from our CI.
However, we couldn't downgrade anymore without causing breakages.

[WarningImHack3r]

@delvh I see. I assume it could only be fixed releasing a new version (1.19.x/1.20) ? Or is it even worse: not being able to fix it until a stable 1.21.0 version?

Have you planned some changes to not make it happen again? It's not the first time :latest is bind to an non-stable version

[wxiaoguang]

I came hear wondering if anyone else's Gitea wasn't working. This must be the reason. My container seems to be continuously trying to restart right now.

Are you using 1.20? 1.20 has some breaking changes, could you share your logs?

[delvh]

I assume it could only be fixed releasing a new version (1.19.x/1.20)

No, as your db will be upgraded with new versions.
You mean a stable 1.20 version, 1.21.0-dev simply means here stopped the development on 1.20 and started the development on 1.21.

[WarningImHack3r]

@delvh so if I get it correctly it won't be fixed until 1.20.0 stable is released?

[delvh]

Yep

[WarningImHack3r]

Have you planned some changes to not make it happen again? It's not the first time :latest is bind to an non-stable version

Ok, and about that @delvh?

[delvh]

Well… We'll try to harden our CI not to set the latest tag anymore on -dev tags, but that is a trial and error process:
The only way to know it works is by releasing something, so we can only hope it won't occur next time again.

[WarningImHack3r]

Don't forget -nightly, -rc* and others! 😄 Thanks for your quick response