This guide explains how to configure the release channel of your Discourse instance.
Required user level: System Administrator
Console access is required.
Managing your Discourse instance’s channel determines the frequency and type of updates you receive. This guide explains the channels available and provides a step-by-step approach to changing the branch on your setup.
Summary
Discourse offers several channels for tracking software updates: latest, release, and esr. This documentation explains the purpose of each, their key features, and how to configure them in your Discourse instance. For an illustration of the channels, see releases.discourse.org.
Supported channels
latest
Recommended Default
This channel provides the latest bug fixes and compatibility updates for plugins. Every passing commit from the main branch is tested by the build server and added to the latest branch after successful verification.
- Suitable for sites that want to stay up to date.
- Sites can update manually at any time.
release
For Sites That Prefer Monthly Releases
The release channel tracks the most recent monthly release of Discourse. Each month, a release branch (e.g. release/2026.2) is cut from latest, providing a stable snapshot.
- Released approximately once per month.
- Each release receives critical fixes for two full release cycles.
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.
Deprecated aliases
For backwards compatibility, the following old branch/tag names still work but are considered deprecated:
-
tests-passed→latest -
beta→release -
stable→esr
Other branches or references
release/YYYY.Mbranches or commit SHAs) is possible but requires expertise. These branches only receive critical fixes for a limited period.
Instructions for configuring your channel
Follow these steps to configure the desired branch in your Discourse instance:
-
Access the configuration file
Open theapp.ymlconfiguration file by running the following commands in your console:
cd /var/discourse
nano containers/app.yml
The nano editor will open the configuration file.
2. Edit the tracking branch
Locate the version parameter by searching for the word “version” in the file:
params:
## Which Git revision should this container use? (default: latest)
#version: latest
- Uncomment the version line.
- Replace
latestwith your desired branch or tag name (e.g.,esr).Example:
params:
## Which Git revision should this container use? (default: latest)
version: esr
- Save and exit
- Press
Ctrl+Oto save your changes. - Press
Enterto confirm. - Use
Ctrl+Xto exit the editor.
-
Rebuild the container
Once the changes are made and saved, rebuild the container to apply the new configuration:
./launcher rebuild app
Last edited by @david 2026-08-03T13:03:06Z
Check document
Perform check on document:
재빌드를 시도해 보고, 만일 뭔가 명확하지 않은 이유로 실패하면 먼저 git pull을 시도해 봅니다. 잠시 걸리긴 하죠.
