[image] I am seeing this update message in my admin panel, but it doesn’t give me the option to update from the site, and mentions I need to use “./launcher rebuild app” to update. I have done that, but it still stays on 3.6.0 beta3. This is in my container/app.yml for the branch. ##Which Git r…

ℹ️ Discourse v3.6.0.beta3-latest — https://github.com/discourse/discourse/commits/9bb15488bd — Ember v6.6.0 BUT…. turns out I’m just an idiot.. disregard this thread. I moved my forum from a dedicated VM to my normal webserver some time ago, and forgot that I did that. I’ve updated it on the webse…

on this occasion, perform a git pull before the rebuild

Why is it needed? Doesn’t a rebuild do a get pull?

Around this time there was a lot of interesting changes around the shift to the new release naming: [이미지] RFC: A new versioning strategy for Discourse Development Those three tags have now been moved to the correct commit manually. Will make sure that the…

[이미지] raskulous: mentions I need to use “./launcher rebuild app” to update. I have done that, but it still stays on 3.6.0 beta3 Are you 100% sure that the rebuild succeeded? No error messages? I can’t think of any reason you’d be left on 3.6.0.beta3 after a successful rebuild :thinking:

The only reason why I didn’t think this might be the issue, is they were apparently still “online” … (which wouldn’t be the case after a failed rebuild)

Yeah that’s true. Although there are situations where launcher rebuild can fail before it shuts down the existing container (e.g. not enough disk space on the machine) The other thing I’d recommend is opening the browser console and checking what the :information_source: line says. It should have a…

[이미지] david: e.g. not enough disk space on the machine) yes, and on that note @raskulous if git pull doesn’t do it, try a ./launcher cleanup app before a rebuild too, for good measure!

root@halflife /var/discourse (main) $ git pull Already up to date. root@halflife /var/discourse (main) $ ./launcher cleanup app WARNING! This will remove all stopped containers. Are you sure you want to continue? [y/N] y Deleted Containers: a58277545d443da8b94056b18921a1f1a075ba0e74cdae77796694c58a…

the rebuild log you see on the console when you ./launcher rebuild app - this is not a log file. … which is long, but ideally you want to look right at the end to see if it raised an error and look further back to find the actual error (if there was one)

Yeah, I don’t see any errors at the end of the launcher rebuild, and it starts up fine. The last few lines remove the old container and start up the new one, no errors there.

2026.1 베타 업데이트

지원 자체 호스팅

david (David Taylor) 2월 19, 2026, 9:51오후 5

재빌드(rebuild)가 성공적으로 완료된 것인지 100% 확신하십니까? 오류 메시지는 없었나요?

성공적인 재빌드 이후에도 3.6.0.beta3에 머물러 있는 이유는 생각나지 않습니다

글		댓글	조회수
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	488	8월 8, 2024
./launcher rebuild app command not found Self-hosting	6	2728	9월 10, 2019
./launcher rebuild app for old 1.6 discourse not working Self-hosting	12	907	1월 25, 2023
Upgrade link no longer works Self-hosting	7	974	11월 22, 2021
Error upgrading Self-hosting	12	1699	10월 20, 2016

2026.1 베타 업데이트

Related topics