[opgelost] Hoe voorkom ik dat ik -dev versies krijg bij het updaten?

AI-generated summary

jhf2442 asked how to avoid installing -dev versions when updating Discourse, concerned they are less stable. Moin clarified that since Discourse 3.2, all test-passed builds—including those ready for production—carry the -dev suffix to distinguish them from beta releases; it doesn’t indicate instability. Moin provided links to guides on configuring tracking branches and understanding release channels, as well as the rationale for the -dev suffix. The key takeaway: -dev versions are safe for production if they’re from the test-passed branch; to avoid unintended versions, explicitly set your desired branch in app.yml or via launcher.

Hi,

I rebuilt my site as there was a newer version available. Looks like I waited too long, so instead of getting a regular version, I got a -dev one.
Documentation states that -dev versions are somehow OK-ish, but not fully tested for release.
Question: how do I prevent the upgrade from selecting a -dev version ? launcher seems not to have a parameter for this, nor does the app.yml

Many thanks

All versions of tests-passed have the -dev suffix at the end since that was added to allow easier differentiation between ā€œbetaā€ releases and the test-passed branch. So the suffix doesn’t mean anything changed in terms of whether the software is ready for use in production. It just means ā€œthis is one version during the development of betaX.ā€

This is the guide about how to change the branch you are on:

And some more information about the different options:

and the topic about the -dev suffix: