As I might for many open-source projects, I was looking for GitHub releases. Someone had the same idea as me and also discovered that Discourse doesn’t have GitHub Releases (anymore).
My next attempt was to use git tags on GitHub, which would be the next best thing. As of today, the latest tag on GitHub is v3.6.0.beta2. Taking a peak at the admin page of my own Discourse instance, I am running v3.6.0.beta3. This means that not only is the latest Discourse release not tagged on GitHub, Discourse itself (the software) must not be using GitHub tags as the way to know when there’s a new release.
I remembered that my install is running on Docker, so I decided to follow that rabbit hole over to where the Discourse images are hosted on Docker Hub. There’s a couple of naming conventions being used as tags there (such as 2.0.20251113-0018-web-only-stable), none that seem to correlated to the v.X.Y.Z format Discourse uses publicly.
So, does anyone have a recommendation on how to do this?
I guess you are running beta3-latest, which means one version during the development of beta3. The final version of beta3 has not yet been released, so the tag represents the latest released beta. But you probably use latest, which is not based on the beta releases.
Have you read the topic about the new versioning strategy?