Links not appearing since the last theme component update

[Moin]

@ToddZ

I can’t find any docs explaining the beta release progression/situation.

Understanding Discourse release channels

This guide explains the different types of Discourse releases and how different channels are used for updates. Required user level: All users Release channels Discourse has four primary release channels, each serving a different purpose: main, latest[1], beta, and stable. The default channel used when installing a production version of Discourse is latest. The naming conventions used by Discourse differ a bit from other software companies: main On GitHub…

As you can read there, you only get notified to update when there is a new milestone. If you were told to update after every commit, that would be several times a day.
When you notice a bug it’s always good to update first to check whether it was already fixed.

I also like Finding what version of Discourse you're using as an explanation how you can check your exact version on GitHub. Of coure as an admin you don’t need the html view.

Here is the explanation for -dev

From Discourse 3.2: adding -dev suffix to beta versions under active development

On tests-passed, starting with 3.2.0.beta1-dev, Discourse core version numbers will include a -dev suffix to indicate that they’re not the final ‘release’ versions of a beta. This suffix doesn’t appear in the UI, so this is a technicality which will have no impact on the vast majority of people. For the technical details, see below: In the beta series for Discourse 3.1 and below, our versioning strategy was to ‘release’ a beta, and then leave the version number in tests-passed exactly the sam…