Pulling latest tag does not pull latest version

[TrousersRippin]

Pre-submission Checklist

• I have searched the existing issues and this bug has not been reported yet
• I have tested this issue on the demo site or the latest version

Where did you encounter this bug?

Latest stable version (self-hosted)

Memos Version

0.25.3

Bug Description

When you use the tag 'latest' in docker-compose it actually pulls a much older version. It would be great if you followed the norm of 'latest' actually meaning the latest release.

Steps to Reproduce

1. docker pull ghcr.io/usememos/memos:latest
2. get older version

Expected Behavior

1. docker pull ghcr.io/usememos/memos:latest
2. get latest release

Screenshots & Additional Context

No response

[GravityEcho]

As a person who also uses docker compose I've been troubled by this kind of issue but I don't believe it is limited to memos, seems to me to be a docker issue. To explain I have RSS feeds of my favorite containers so when they release I know about it within hours. Its not all that important though because if I try to install the latest container immediately docker usually just installs the current version for probably a good 24 - 48 hours. Because of this I run a weekly script that dumps all my containers docker stop $(docker ps -aq) and then docker prune -a and then installs them all fresh again. The ones tagged latest get auto updated and I have not noticed any such problem with memos, I'm on the latest version using :latest. You might try completely wiping memos from docker with a prune command and then trying to install :latest.

[GravityEcho]

and then I checked my compose, for memos its :stable not :latest but using :stable should have the same effect.

[TrousersRippin]

Yes for this software stable = latest. I just think latest tag should in fact be the latest stable release version.