# ESR Usage Help

**URL:** https://meta.discourse.org/t/esr-usage-help/401203
**Category:** Support
**Created:** [April 21, 2026, 8:55pm UTC](https://meta.discourse.org/t/esr-usage-help/401203 "2026-04-21T20:55:38Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [April 21, 2026, 9:13pm UTC](https://meta.discourse.org/t/esr-usage-help/401203/4 "2026-04-21T21:13:17Z")

</div>

I think now such a change would be handled using the [upcoming changes feature](https://meta.discourse.org/t/upcoming-changes/395390)

> [@haydenjames](#):
>
> Since the new release model, there have been a lot of changes and it keeps throwing settings around.

This change happened before the new release structure was introduced

> [@haydenjames](#):
>
> Also, side note, I can’t hit enter anymore (for a new line) after `**:` it puts an emoji. This was not the case previously. Is this already a known bug, or do I need to report it?:
> 
> ![image](https://global.discourse-cdn.com/meta/original/4X/7/c/a/7cafbc98e576de0c18cbbca1c739eb7e2f10425e.png)

I think it only happened because you have the asterisk in front of the colon.

ESR is what stable used to be before. But there were also quite frequent updates for that because there were lots of security fixes in the past months

> [@Understanding Discourse release channels](https://meta.discourse.org/t/understanding-discourse-release-channels/264400/1):
>
> ### esr
> 
> ESR stands for **Extended Support Release**. Approximately every 6 months, one of the monthly releases is designated as an ESR. ESR versions receive critical security fixes for a longer period — they remain supported for 2 releases after the _next_ ESR is declared.
> 
> On GitHub: [GitHub - discourse/discourse at esr · GitHub](https://github.com/discourse/discourse/tree/esr)
> 
> The tag `esr` always points to the latest ESR release. For backward compatibility, the `stable` branch and tag are aliased to `esr`.
> 
> The ESR channel is not necessarily more “stable” than **latest**. It’s more about the idea that the bugs are known, and it serves as a checkpoint for a specific set of features and improvements. With **latest** , there may be new bugs introduced, then fixed a few commits later.

> [@Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/configure-a-supported-tracking-branch-to-get-discourse-software-updates/17014/1):
>
> ### `esr`
> 
> ℹ **Extended Support Release**
> 
> The `esr` tag tracks the latest Extended Support Release, intended for sites prioritizing long-term stability and security over frequent updates.
> 
> - Declared approximately every 6 months from the monthly releases.
> - Receives security fixes and critical backports for an extended period.
> - May have limited compatibility with community plugins and theme components.
> 
> > ⚠ **Note:** Not receiving regular maintenance updates can leave some features outdated or visually inconsistent.

---

_[View the full topic](https://meta.discourse.org/t/esr-usage-help/401203)._