I had a long-standing issue with a Discourse install that was stuck at v2.9.0.beta1—due to personal challenges, I couldn’t resolve it for years. Back then, it seemed impossible to move to v2.9.0.beta2. Recently, while troubleshooting a rebuild problem, I commented out certain hooks in my app.yml (sp…

You can take a look at this guide: [이미지] Configure a supported tracking branch to get Discourse software updates Self-Hosting bookmark This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates. pers…

Change tests-passed to stable in your app.yml. If you don’t have that in your yml you can look at the samples directory.

Thanks, so I had: ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed I updated it to be: ## Which Git revision should this container use? (default: tests-passed) version: stable After rebuild, the system is now at: 3.5.0.beta1-dev Which seems…

[이미지] M. Reacher: After rebuild, the system is now at: 3.5.0.beta1-dev It would appear that you changed the version to stable after the rebuild. You’re beyond stable now, so you’ll need to change it to beta or tests-passed until the next stable release (and since there was one in the past wee…

No, unfortunately I did not… I am 100% certain of this, it was on 3.4.0.beta4-dev and then I changed the app.yml and then did the rebuild. Then 3.5.0.beta1-dev showed up. This is 100% the path that was followed… I have ZERO doubt just to be clear about this. I literally verified things prior to the …

[이미지] M. Reacher: and then I changed the app.yml and then did the rebuild. Does the line with tests-passed in it start with a #?

Screenshot of the editor: <a class="lightbox" href="https://global.discourse-cdn.com/meta/original/4X/f/2/c/f2ca87bd9d58c1b6dc3a8ca173b8bdc7be419aa4.png" data-download-href="/uploads/short-url/yDPsWGEptaCcpY2uJQM5QbVLBsg.png?dl=1" title="This image displays a configuration script snippet with details on setting database, Git repository, and memory settings, specifically selecting the English language and using the stable version in a system environment. (Captioned by AI)" rel="noopener nofollow ugc">[This image displays a configuration script snippet with details on setting database, Git repository, and memory settings, specifically selecting the English language and using the stable version in a system environment. (Captioned by AI)]

It’s commented out, so what you put there does not matter and the default is tests passed. When you rebuilt to rebuilt to the latest tests passed

Thanks again for your help @pfaffman . To summarize my current understanding: Our instance was running 3.4.0.beta4-dev, which is not considered a stable release. When I updated my configuration to use version: stable (with the default commented out), I expected that future rebuilds would lock the i…

[이미지] Jay Pfaffman: It’s commented out Hmm. Doesn’t look like it to me: [image]

v2.9.0.beta1에서 멈춤 – Hooks 비활성화 후 3.4.0.beta4-dev 실행 중: 안정판으로 고정하는 방법?

지원

pfaffman (Jay Pfaffman) 2월 8, 2025, 6:15오후 12

Doh! Maybe I looked too fast on my phone. I have no explanation for how I missed that nor how the site is now running 3.5.0.beta1-dev.

글		댓글	조회수
Secure way to configure upgrading to only stable version of forum releases? Self-hosting stable	10	1549	2월 6, 2024
Is it possible to upgrade Discourse up to a number of commits in the version? Development	4	2053	6월 25, 2019
Upgrade Button - Possible Window to Exploits Feature	4	1731	9월 10, 2014
Switch from beta to stable releases Support	4	3070	9월 5, 2019
How to avoid Discourse BETA version and keep only stable? Support	1	988	7월 28, 2020

v2.9.0.beta1에서 멈춤 – Hooks 비활성화 후 3.4.0.beta4-dev 실행 중: 안정판으로 고정하는 방법?

Related topics