We’re planning to introduce a new versioning system for Discourse. Our goal is to provide more choice & predictability for community administrators, while maintaining our development velocity. We’re also adjusting some terminology to align better with other software. This document will evolve as we…

Hi @simonk , thanks for raising those points! We’ve actually been discussing both those things today internally. The old beta and latest-release tags should be aliases of release release should be tracking the latest commit of release/2025.11 Working on getting that fixed up right now.

Those three tags have now been moved to the correct commit manually. Will make sure that the automated tooling is updated to keep them in the right place going forward. * commit 48167b94d63faf8a41b9c8193ec5dd3e4e9f498e (HEAD -> release/2025.11, tag: release, tag: latest-release, tag: beta, origin/r…

A production quirk. My self-hosted Discourse was still showing 3.6.0.beta2 as the most recent release. In the Admin Dashboard, the green smiley face indicated I was on the latest release, but in reality, I was two releases behind. I performed a manual update and am now on 2025.12.0-latest. Is the…

So this is probably because of the transition from one scheme to the new one, but yesterday 3.5.4 was released 3.5 is marked ESR and was released in August 2025 yesterday 2026.1 was released which is an ESR version [이미지] david: ESR versions remain supported for 2 releases after the next ESR i…

[이미지] RGJ: this is probably because of the transition from one scheme to the new one Yeah that’s correct. Stable 3.5 doesn’t have its own branch in git, so continuing to support it after converting the stable branch to a tag is tricky. We did tag v3.5.4 (which includes the latest security fix…

[이미지] david: 在您的 app.yml 文件中设置 version: release/v2026.02 我想知道这个具体的配置示例是什么样的？ env: DISCOURSE_VERSION: bd4e34ec04 还是 version: bd4e34ec04

[image] 我想安装 ESR 版本，应该怎么做。现在默认安装的都是最新的版本。

IIRC you can set version to stable.

是的，我刚找到可以在 templates/web.template.yml 中设置 params: version: esr

Hmm… does Understanding Discourse release channels need to be changed then?

RFC: Discourse를 위한 새로운 버전 관리 전략

개발

Moin 3월 20, 2026, 8:01오전 58

그렇게 생각합니다. David가 이전에 문서화에 대해 언급한 적이 있습니다.

글		댓글	조회수
January 2026 Releases Announcements release-notes	15	1443	2월 3, 2026
July 2026 monthly release Announcements release-notes	13	590	7월 29, 2026
Jumping from 2026.1 ESR to 2026.7 - What I found Support	5	270	7월 29, 2026
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	37	2891	2월 3, 2024
Enable updates only to a given release UX	28	3405	1월 25, 2017

RFC: Discourse를 위한 새로운 버전 관리 전략

Related topics