Warum bin ich auf beta3-dev und nicht auf Tests-Passed (wie in meiner web_only.yml festgelegt)?

[Bathinda (Bathinda Helper)]

My web_only.yml clearly has parameters set as/for: Tests-Passed builds.

But still my website’s Admin dashboard shows: beta3-Dev build.
‘Dev’ word is still there, even after rebuilding my container just now,nothing changed.

I’d rather like to stay with ‘Tests-Passed’ builds.

[Jagster (Jakke Lehtonen)]

AFAIK you are. It could be because of this:

@Canapin

tests-passed

It includes features and improvements from the main channel that have undergone a certain level of testing. It has the best balance between stability and access to the latest improvements.
It is not much different than most other software releases out there, which usually release small changes every two weeks. We commit new changes almost daily instead, and they’re available via tests-passed.

[pfaffman (Jay Pfaffman)]

A month or so ago they started adding dev to the version to indicate that the version you see doesn’t necessarily mean the beta query that version. I think there was an announcement, but I but can’t find it in the add link modal.

[Jagster (Jakke Lehtonen)]

This one perhaps?

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…

[Jagster (Jakke Lehtonen)]

@pfaffman

but can’t find it in the add link modal

Try term beta