# 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 20:10:06 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:** 7

<div class="post-metadata">

**Author:** ![Json\_Blob](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/json_blob/32/119534_2.png) [@Json\_Blob](https://meta.discourse.org/u/Json_Blob)\
**Post date:** [19.Июнь.2019 21:48:14 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/7 "2019-06-19T21:48:14Z")

</div>

That makes more sense, ok, so it sounds like the advised path forward if my group decides to take an update is to get onto the “tests-passed” branch and off beta. Is that summation correct? In which case I follow Jeff’s instructions above for the YML adjustment

---

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