# Stable version upgrade to 2.4.0

**URL:** https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780
**Category:** Support
**Created:** [February 27, 2020, 1:07pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780 "2020-02-27T13:07:05Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![rysher](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@rysher](https://meta.discourse.org/u/rysher)
#### Post date: [February 27, 2020, 1:07pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/1 "2020-02-27T13:07:05Z")

</div>

I have Discourse v2.3.9 with “version: stable” param in app.yml and would like to continue to use ‘stable’ version.

Dashboard shows that v2.4.0 is out, but when I go to Upgrade section, I see the following:

#### 

New Version Available!

- Remote Version: v2.4.0.beta11 +737
- Last Updated: 15 hours ago
- [2616 new commits](https://github.com/discourse/discourse/compare/9298132c73...76b9be3f19)

Does it mean that Discourse will be upgraded to the recent test-passed version? As I understand from the commits master was merged into stable and it is a minor version upgrade. But why do I see “…beta11” there?

Thanks.

---

<div class="post-metadata">

### Author: ![frictionel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frictionel/32/299701_2.png) [@frictionel](https://meta.discourse.org/u/frictionel)
#### Post date: [February 27, 2020, 6:06pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/2 "2020-02-27T18:06:36Z")

</div>

I was wondering the same but when you look at the list of commits, the last one is:

 ![Screenshot 2020-02-27 at 19.01.39](https://global.discourse-cdn.com/meta/original/3X/6/9/69cebd9ad9bd64da0f997f9efadd7f401cfaf130.png)

which suggests that the Version displayed in Discourse is not the “correct” one. Well maybe it is correct because the stable release is the same as v2.4.0.beta11 +737?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 27, 2020, 7:49pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/3 "2020-02-27T19:49:54Z")

</div>

Are we all good here @neil?

---

<div class="post-metadata">

### Author: ![neil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neil/32/102150_2.png) [@neil](https://meta.discourse.org/u/neil)
#### Post date: [February 27, 2020, 8:11pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/4 "2020-02-27T20:11:04Z")

</div>

It should be fixed now.

I had tagged `v2.4.0` commit in stable, but then we delayed the release by a day, so when I did the bump the next day I updated the timestamp on the commit and then pushed it and the new tag. But bumping the timestamp in git creates a new commit. The v2.4.0 tag was on an orphaned commit, so `git describe HEAD 2>/dev/null` was finding the wrong tag. Anyway, it’s fixed.

---

<div class="post-metadata">

### Author: ![rysher](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@rysher](https://meta.discourse.org/u/rysher)
#### Post date: [February 27, 2020, 8:12pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/5 "2020-02-27T20:12:57Z")

</div>

Thank you! It is fixed for me now too.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 27, 2020, 9:10pm UTC](https://meta.discourse.org/t/stable-version-upgrade-to-2-4-0/142780/6 "2020-02-27T21:10:18Z")

</div>