# Upgrade Button - Possible Window to Exploits
**URL:** https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877
**Category:** Feature
**Created:** [September 10, 2014, 4:14pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877 "2014-09-10T16:14:17Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Omni](https://meta.discourse.org/u/Omni)
#### Post date: [September 10, 2014, 4:14pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/1 "2014-09-10T16:14:17Z")
I’m sure that many of you recently received an e-mail stating:
> A new version of Discourse is available.
> Your version: 1.0.0
> New version: 1.0.1
I went to upgrade and wound up with this:
> Version 1.1.0.beta1 1.1.0.beta1 🙂 Looks like you upgraded recently. Fantastic!
Yes, I understand that there are ways to upgrade manually, but I firmly believe that the simple 1-click upgrade button should not install an unstable version of Discourse.
If anything, there should be an option to install the _latest stable_ and _latest unstable_ version.
Either that, or the button should simply avoid the beta release altogether.
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [September 10, 2014, 4:17pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/2 "2014-09-10T16:17:17Z")
Um… you have that ability. If you are seeing 1.1.0.beta1 you are subscribed to the tests-passed branch and not the stable branch.
> [@Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/change-tracking-branch-for-your-discourse-instance/17014):
>
> bookmark This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates. person_raising_hand Required user level: System Administrator warning Console access is required. Managing your Discourse instance’s tracking branch determines the frequency and type of updates you receive. This guide explains the different tracking branches available and provides a step-by-step approach to changing the branch on your setup. Summary Disco…
---
### Author:  [@Omni](https://meta.discourse.org/u/Omni)
#### Post date: [September 10, 2014, 4:21pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/3 "2014-09-10T16:21:47Z")
Thanks for the valuable information.
The install came from the [Official Discourse Docker Image](https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md).
I’m now curious as to why this image has defaulted to subscribe to the tests-passed branch.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [September 10, 2014, 10:37pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/4 "2014-09-10T22:37:51Z")
That is what we believe most people should be on.
Our tests-passed builds are quite stable, you’re using the latest one _right now_.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [September 10, 2014, 10:41pm UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/5 "2014-09-10T22:41:49Z")
> [@Omni](#):
>
> there should be an option to install the latest stable and latest unstable version.
This is complicated from the web UI for a couple of reasons
1. You can not move back to “stable” after being on “tests-passed” until the next major release
2. The web runs in the container, it would have to reach out of the container to make that change
What we can do is link to all this information from the web UI so people are not surprised.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [December 4, 2025, 11:32am UTC](https://meta.discourse.org/t/upgrade-button-possible-window-to-exploits/19877/6 "2025-12-04T11:32:24Z")