# Reverting version after problematic update

**URL:** <https://meta.discourse.org/t/reverting-version-after-problematic-update/240656>\
**Category:** Self-hosting\
**Created:** [October 1, 2022, 5:51pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656 "2022-10-01T17:51:29Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [October 2, 2022, 5:55pm UTC](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656/12 "2022-10-02T17:55:14Z")

</div>

If you were on tests-passed then a fresh 2.8 beta 9 install work won’t work for you, which is why you can’t use `v2.9.0.beta9` as suggested by someone else above. As the name indicates, `tests-passed` is the latest version of merged changes which has passed the requisite suite of tests.

You’re going to need to pin the exact version of Discourse in your app.yml by inspecting your backup file.

If the plugins you use have been updated since the build in your backup then you may also need to pin those versions in the plugin section of your `app.yml`.

---

_[View the full topic](https://meta.discourse.org/t/reverting-version-after-problematic-update/240656)._