[resuelto] Cómo evitar conseguir versiones -dev al actualizarse?

[Moin]

Todas las versiones de tests-passed tienen el sufijo -dev al final, ya que se añadió para permitir una diferenciación más fácil entre las versiones “beta” y la rama test-passed. Por lo tanto, el sufijo no significa que algo haya cambiado en cuanto a si el software está listo para su uso en producción. Simplemente significa “esta es una versión durante el desarrollo de betaX”.

Esta es la guía sobre cómo cambiar la rama en la que te encuentras:

Configure a supported tracking branch to get Discourse software updates

This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates. Required user level: Systen Administrator Console access is required. Managing your Discourse instance’s tracking branch determines the frequency and type of updates you receive. This guide explains the different tracking branches available and provides a step-by-step approach to changing the branch on your setup. Summary Disco…

Y más información sobre las diferentes opciones:

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…

y el tema sobre el sufijo -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…