# Introducing releases.discourse.org

**URL:** https://meta.discourse.org/t/introducing-releases-discourse-org/392712
**Category:** Announcements
**Created:** [January 6, 2026, 3:27pm UTC](https://meta.discourse.org/t/introducing-releases-discourse-org/392712 "2026-01-06T15:27:56Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [January 7, 2026, 2:50am UTC](https://meta.discourse.org/t/introducing-releases-discourse-org/392712/7 "2026-01-07T02:50:04Z")

</div>

> [@david](#):
>
> Adding changes from other repositories is something we might consider in future, but there aren’t any immediate plans to implement it.

Another thing to note about this: we have plans in [the RFC](https://meta.discourse.org/t/383536) to build out some automation for plugins and themes to create branches compatible with different versions of Discourse.

I think the time to circle back to this would be after we get that in place.

> [@jordanjay29](#):
>
> With the extra information between release and active development for versions, is there any setting (or plan to add one) to keep Discourse on a release or ESR version?

This is possible to do now by setting the branch to track in your deployment config:

But once you do, you’re kind of pinned on that release forever. What we still need to build is a better way to see when a new release is available (on whichever release channel you’re following).

We have had some early discussions about how this might work, but are still discussing the details.

---

_[View the full topic](https://meta.discourse.org/t/introducing-releases-discourse-org/392712)._