# Version check for new stable release?
**URL:** https://meta.discourse.org/t/version-check-for-new-stable-release/111558
**Category:** Feature
**Created:** [March 14, 2019, 8:47am UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558 "2019-03-14T08:47:32Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@RalfJung](https://meta.discourse.org/u/RalfJung)
#### Post date: [March 14, 2019, 8:47am UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/1 "2019-03-14T08:47:32Z")
I’d like to run the latest stable version of Discourse, but not install beta versions. Currently, I get an email from my Discourse instance any time there’s a new beta, but that’s not helpful – and there is no email for new stable versions. I tried subscribing to GitHub’s “releases” for the Discourse repo, but there I am getting no email at all (which is of course not your fault, but would have been a way to mitigate this).
Is there any way to configure the built-in update check if Discourse to only take newer stable releases into account? If not, is there any chance this option might be added in the future?
---
### Author:  [@venarius](https://meta.discourse.org/u/venarius)
#### Post date: [March 14, 2019, 9:09am UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/2 "2019-03-14T09:09:05Z")
Change app.yml `version` from “tests-passed” to “stable”. That should only notify you if a new stable version is ready then 🙂
---
### Author:  [@RalfJung](https://meta.discourse.org/u/RalfJung)
#### Post date: [March 14, 2019, 9:54am UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/3 "2019-03-14T09:54:35Z")
I currently had it set to the latest stable version manually, and that was not enough – but maybe that’s a fallback behavior.
I’ll try this, thanks!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 14, 2019, 1:32pm UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/4 "2019-03-14T13:32:13Z")
If you’re already on `tests-passed` you won’t be `stable` until the next `stable` release. Note that in some ways `tests-passed` is more stable than `stable` as it’s what [discourse.org](http://discourse.org) runs, so it’s the best tested.
---
### Author:  [@RalfJung](https://meta.discourse.org/u/RalfJung)
#### Post date: [March 14, 2019, 1:45pm UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/5 "2019-03-14T13:45:30Z")
I was previously hopping from tag to tag. Seems like when built for `v2.2.3`, Discourse interprets this as looking for beta updates, not stable updates. Not sure if anything can be done about that?
Now I remember why I wasn’t on `stable`: that one can actually end up not corresponding to a tag, like currently it is one commit ahead of the latest release. Oh well.
> [@pfaffman](#):
>
> Note that in some ways `tests-passed` is more stable than `stable` as it’s what [discourse.org](http://discourse.org) runs, so it’s the best tested.
Fair. On the other hand, I don’t want to have to update quite so often.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 14, 2019, 1:54pm UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/6 "2019-03-14T13:54:05Z")
Have you rebuilt since changing your app.yml from tests-passed to stable?
If not please don’t try to until stable catches up, as downgrading is totally unsupported and can ruin your database.
As @pfaffman has already mentioned, being on tests-passed is usually the safer option.
---
### Author:  [@RalfJung](https://meta.discourse.org/u/RalfJung)
#### Post date: [March 14, 2019, 2:28pm UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/7 "2019-03-14T14:28:48Z")
> [@Stephen](#):
>
> Have you rebuilt since changing your app.yml from tests-passed to stable?
I haven’t been on `test-passed` since forever. I was on `v2.2.0` until this morning and then moved to `v2.2.3` just before starting this thread.
> [@Stephen](#):
>
> is totally supported
I suppose you mean **un** supported.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 14, 2019, 3:11pm UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/8 "2019-03-14T15:11:28Z")
Right, so when you said:
> [@RalfJung](#):
>
> I’d like to run the latest stable version of Discourse, but not install beta versions.
It suggests you currently aren’t.
> [@RalfJung](#):
>
> I suppose you mean **un** supported.
Correct, fat fingers+autocorrect bested me there.
---
### Author:  [@RBoy](https://meta.discourse.org/u/RBoy)
#### Post date: [February 23, 2024, 4:55am UTC](https://meta.discourse.org/t/version-check-for-new-stable-release/111558/9 "2024-02-23T04:55:23Z")
I was looking at this post about using a specific version:
> [@How would I install a certain (old) version of Discourse](https://meta.discourse.org/t/how-would-i-install-a-certain-old-version-of-discourse/166423/4):
>
> Checkout the same version of discourse\_docker that you use on your other server, maybe copy your app.yml from the old server and make the necessary changes. Also in app.yml, change the version from tests-passed to either a tag (e.g. v2.5.0.beta7) or use a git commit hash.
When I look at github I see `stable` or `tests-passed` branches (not tags). However I do see a `latest-release` tag. What’s the difference between `stable` (branch) and `latest-release` (tag)?