Users rysher and frictionel noticed that Discourse’s upgrade interface showed “v2.4.0.beta11 +737” despite being on the stable branch, raising confusion about whether they’d be upgraded to a beta version. codinghorror checked in with neil, who confirmed a tagging issue: the v2.4.0 tag had been applied to an orphaned commit after a timestamp bump created a new commit, causing git describe to return the wrong version. Neil fixed the tag, and rysher confirmed the correct version now displays. The stable branch now correctly reflects the official v2.4.0 release.
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?
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?
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.