# Is it possible to upgrade Discourse up to a number of commits in the version?

**URL:** https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386
**Category:** Development
**Created:** [07.Июнь.2016 16:28:49 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386 "2016-06-07T16:28:49Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![stevenpslade](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stevenpslade/32/53550_2.png) [@stevenpslade](https://meta.discourse.org/u/stevenpslade)
#### Post date: [07.Июнь.2016 16:28:49 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386/1 "2016-06-07T16:28:49Z")

</div>

I currently work with a development, staging, and production version of Discourse. My development version is always on `tests-passed` so that features I am working on will definitely work on the most recent version.

I then add, let’s say a plugin, to my staging Discourse and concurrently upgrade my staging Discourse to the latest version (ex: `1.6.0.beta7`). If all goes well, I do the same for production. So essentially dev is on `tests-passed` and the other two are forced on the last upgrade.

I have recently encountered a problem where my dev Discourse is on version `1.6.0.beta7 +179`. Somewhere in those 179 commits, a change was made that _helps_ one of my plugins to work. So on my staging, version `1.6.0.beta7` (not including the +179 commits) the plugin is broken.

So in short, can I set the version of a Discourse to `1.6.0.beta7 +179` somehow?

**Edit:** If specify the build would that do the trick? Something like: `1.6.0.beta7, build: bfc8b3362b`

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [07.Июнь.2016 17:05:49 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386/2 "2016-06-07T17:05:49Z")

</div>

Refer to this topic:

> [@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…

You could try using the version (commit ID) found either [on github](https://github.com/discourse/discourse/commits/master) or in your development page source…

So viewing the source of this page currently:

```HTML
<meta name="generator" content="Discourse 1.6.0.beta7 - https://github.com/discourse/discourse version b624c5cc9403d58d8d45125d7f70e60cddbb9ab9">

```

I can see the version is `b624c5cc9403d58d8d45125d7f70e60cddbb9ab9`, this is the ID you could try using [in place of `tests-passed`](https://meta.discourse.org/t/change-tracking-branch-for-your-discourse-instance/17014) on your staging / production.

To be clear - I’ve not tested using a commit ID - but it should work.

---

<div class="post-metadata">

### Author: ![stevenpslade](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stevenpslade/32/53550_2.png) [@stevenpslade](https://meta.discourse.org/u/stevenpslade)
#### Post date: [07.Июнь.2016 18:15:42 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386/3 "2016-06-07T18:15:42Z")

</div>

Thanks, I’ll try this and let you know how it goes. I think another way of getting the version id is going to the admin dashboard and clicking on the version you are on. It will link you to the Discourse git repo with the specified version in the url.

**UPDATE:** It worked! 🎊

---

<div class="post-metadata">

### Author: ![ljpp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ljpp/32/96506_2.png) [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [25.Июнь.2019 08:54:22 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386/4 "2019-06-25T08:54:22Z")

</div>

Bonkers, it looks like I missed the 2.2 major upgrade in one of my small playground instances and now the stable branch is already in 2.3.

What I understood from above is that it is possible to update to a specific release/version, but what exactly I should replace _stable_ with in my app.yml ?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [25.Июнь.2019 12:44:13 UTC](https://meta.discourse.org/t/is-it-possible-to-upgrade-discourse-up-to-a-number-of-commits-in-the-version/45386/5 "2019-06-25T12:44:13Z")

</div>

You can put the commit id or a tag.
