# Feature/Bugfix announcement topics should include version number
**URL:** https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394
**Category:** Site feedback
**Created:** [April 10, 2026, 12:58pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394 "2026-04-10T12:58:06Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jrgong](https://meta.discourse.org/u/jrgong)
#### Post date: [April 10, 2026, 12:58pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/1 "2026-04-10T12:58:06Z")
Hey guys
First of all, it’s fantastic that so many new features and bugfixes are shipped for Discourse. I really appreciate all the hard work and implementation speed.
With that, it’s getting increasingly hard to keep track which featured and which bug fix will be added to which release version of Discourse.
[Example topic](https://meta.discourse.org/t/pin-chat-messages-for-increased-visibility/397571) and its current state:
> [@Pin chat messages for increased visibility](https://meta.discourse.org/t/pin-chat-messages-for-increased-visibility/397571/1):
>
> You can now pin chat messages in Discourse so you can make important messages more visible to other channel members.
>
> In this topic, we’ll review the major changes and share how you can start using this today.
>
> ## 🔬 What’s changed
>
> By default, when chat pinning is enabled, admins and moderators can pin any message in the chat channel by hovering over the message (or long-pressing on mobile), clicking the vertical ellipsis button, and selecting the Pin message button.
Here an additional “Meta” callout would be helpful to understand which Discourse version has that feature and in what state (final/experimental/…)
e.g.
> [@Pin chat messages for increased visibility](https://meta.discourse.org/t/pin-chat-messages-for-increased-visibility/397571/1):
>
> **🤖 v.2026.n.n - #experimental**
>
> You can now pin chat messages in Discourse so you can make important messages more visible to other channel members.
>
> In this topic, we’ll review the major changes and share how you can start using this today.
>
> ## 🔬 What’s changed
>
> By default, when chat pinning is enabled, admins and moderators can pin any message in the chat channel by hovering over the message (or long-pressing on mobile), clicking the vertical ellipsis button, and selecting the Pin message button.
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [April 10, 2026, 1:04pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/2 "2026-04-10T13:04:28Z")
> [@jrgong](#):
>
> With that, it’s getting increasingly hard to keep track which featured and which bug fix will be added to which release version of Discourse.
I confused because so long as you are on `tests-passed` you should be able to install most (if not all) of these same-day if you’d like. Versions are not really relevant for much besides knowing the last time an installation was synced with git.
---
### Author:  [@jrgong](https://meta.discourse.org/u/jrgong)
#### Post date: [April 10, 2026, 1:23pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/3 "2026-04-10T13:23:55Z")
We are currently on managed hosting with @RGJ, and as such, we update irregularly based on their deployment cycles.
Consequently, it would be helpful for us to know the specific version for each feature announced here…
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [April 10, 2026, 1:27pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/4 "2026-04-10T13:27:56Z")
I think you can usually find out yourself.
The topic in your example was published at the beginning of March. So, let’s take a look at [releases.discourse.org](http://releases.discourse.org)
After the release of a version, no new features are added. It only receives security and other critical fixes. So, a feature announced in March will probably not work on v2026.1 and v2026.2 (In this case, it may work on v2026.2 because it was merged a few days earlier than the announcement).
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [April 10, 2026, 1:50pm UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/5 "2026-04-10T13:50:45Z")
> [@darkpixlz](#):
>
> so long as you are on `tests-passed` you should be able to install most (if not all) of these same-day if you’d like
With tens of theme components and a large number of third party plugins like @jrgong has, this is not realistic - at all. There are too many breaking changes in Discourse and testing alone takes many hours.
---
### Author:  [@jrgong](https://meta.discourse.org/u/jrgong)
#### Post date: [April 11, 2026, 11:48am UTC](https://meta.discourse.org/t/feature-bugfix-announcement-topics-should-include-version-number/400394/6 "2026-04-11T11:48:23Z")
I do that already, but since it’s already maintained in the releases page (which is awesome btw!), linking each object (feature/bug/etc) to the meta announcement topic would he helpful already so that the version number can be added to the individual post as a prefix or similar