# Problem with Upgrade \[error 137\]

**URL:** https://meta.discourse.org/t/problem-with-upgrade-error-137/293652
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [January 31, 2024, 4:33pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652 "2024-01-31T16:33:52Z")
**Posts on this page:** 1
**Showing post:** 21

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 2, 2024, 12:59am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/21 "2024-02-02T00:59:34Z")

</div>

> [@anon36555649](#):
>
> only stable tested updates not the developer/beta ones

Did you read about the meaning of those?

> [@Understanding Discourse release channels](https://meta.discourse.org/t/why-does-discourse-always-install-beta-versions-by-default/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 …

> [@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…

---

_[View the full topic](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652)._
