# \[solved\] How to avoid getting -dev versions when updating?
**URL:** https://meta.discourse.org/t/solved-how-to-avoid-getting-dev-versions-when-updating/344864
**Category:** Support
**Created:** [December 30, 2024, 11:43am UTC](https://meta.discourse.org/t/solved-how-to-avoid-getting-dev-versions-when-updating/344864 "2024-12-30T11:43:21Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jhf2442](https://meta.discourse.org/u/jhf2442)
#### Post date: [December 30, 2024, 11:43am UTC](https://meta.discourse.org/t/solved-how-to-avoid-getting-dev-versions-when-updating/344864/1 "2024-12-30T11:43:21Z")
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
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [December 30, 2024, 11:55am UTC](https://meta.discourse.org/t/solved-how-to-avoid-getting-dev-versions-when-updating/344864/3 "2024-12-30T11:55:07Z")
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:
> [@Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/configure-a-supported-tracking-branch-to-get-discourse-software-updates/17014):
>
> bookmark This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates. person_raising_hand Required user level: System Administrator warning 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…
And some more information about the different options:
> [@Understanding Discourse release channels](https://meta.discourse.org/t/understanding-discourse-release-channels/264400):
>
> bookmark This guide explains the different types of Discourse releases and how different channels are used for updates. person_raising_hand Required user level: All users Release channels Discourse has four primary release channels, each serving a different purpose: main, latest, release, and esr. The default channel used when installing a production version of Discourse is latest. Since November 2025, Discourse uses a date-based versioning scheme: YYYY.MM.PATCH (e.g., v2026.2.0). On …
and the topic about the -dev suffix:
> [@From Discourse 3.2: adding -dev suffix to beta versions under active development](https://meta.discourse.org/t/from-discourse-3-2-adding-dev-suffix-to-beta-versions-under-active-development/273490):
>
> 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…
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [January 29, 2025, 11:55am UTC](https://meta.discourse.org/t/solved-how-to-avoid-getting-dev-versions-when-updating/344864/4 "2025-01-29T11:55:09Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.