Discourse is streamlining its release process by replacing the beta branch with a beta tag that always points to the latest beta version. Users currently tracking the beta branch must manually rebuild their Docker container using git pull and ./launcher rebuild app to adopt the change. Hosted sites are unaffected. For most users, tracking tests-passed is recommended as it provides the latest stable updates and plugin compatibility — and is often what new installations receive by default, even if labeled as “beta”. MikeNolan expressed confusion about calling a production-ready version “beta”, but mcwumbly clarified that tests-passed is the preferred default and referenced a meta discussion explaining why Discourse often uses beta labeling. Users can verify their current version by checking the “version” line in app.ymlpfaffman.
We are streamlining our release process and are removing the beta branch. It will be replaced with a new beta tag that will always point to the latest beta version.
What does this mean for you? If your Discourse instance is currently tracking the beta branch, then you’ll be prompted to rebuild your Docker container on the command line to pick up this change:
cd /var/discourse
git pull
./launcher rebuild app
Afterwards, everything should work as it did before as all involved components have already been updated to support the new beta tag.
Hosted by us? Then there’s no need to worry. This change will not affect your site.
When I built my production site a few weeks ago, I followed the standard instructions to build a new site and what I got was the beta branch. So how do I switch to the the passed tests branch?
Hosted by us? Then there’s no need to worry. This change will not affect your site.
Hosted by us? Then there’s no need to worry. This change will not affect your site.