# Upgrade 2.2 beta to 2.3 release, not 2.4 beta

**URL:** https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838
**Category:** Self-hosting
**Tags:** hosting
**Created:** [19 ביוני,‏ 2019,‏ 8:10pm UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838 "2019-06-19T20:10:06Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![lucasbasquerotto](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lucasbasquerotto/32/133376_2.png) [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)
#### Post date: [20 ביוני,‏ 2019,‏ 12:47am UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/13 "2019-06-20T00:47:11Z")

</div>

Just keep in mind that in some cases the stable branch might stop working with the `discourse-docker` repository.

> [@Help .. rebuild app failed](https://meta.discourse.org/t/help-rebuild-app-failed/84538/15):
>
> Ahh you’re on the stable branch…we might be missing a backport or smth.

> [@Mini\_racer causing rebuild fail](https://meta.discourse.org/t/mini-racer-causing-rebuild-fail/52231/9):
>
> Same issue for me as well. I was on stable, and couldn’t upgrade from 1.6.4 to 1.6.5 because of this issue. Now my forum is down. [https://meta.discourse.org/t/cannot-upgrade-1-6-4-1-6-5/52407?u=zsero](https://meta.discourse.org/t/cannot-upgrade-1-6-4-1-6-5/52407)

The good news is that from what I see in these cases, the discourse team backports the changes to the stable branch for it to work again.

I think that creating **tags and branches in the `discourse-docker` repository** would help a lot to avoid these kind of problems. This is up to the discourse team, tough (or you can fork the repo).

---

_[View the full topic](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838)._