这里应该有一个错误，我尝试通过标签拉取v3.6.0.beta2，结果遇到下面的错误： FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -H -E -u discourse bash -c ' set -o errexit git fetch --tags --prune-tags --prune --force origin if [[ $(git symbolic-ref --short HEAD) == v3.6.0.beta2 ]] ; then git pull else git -c advice.detachedHead=false checkout v3.6.0.beta2 fi ' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:138:in 'Pups::ExecCommand#spawn' exec failed with the params {"cd" => "$home", "hook" => "code", "cmd" => ["sudo -H -E -u discourse git clean -f", "sudo -H -E -u discourse bash -c '\n set -o errexit\n git fetch --tags --prune-tags --prune --force origin\n if [[ $(git symbolic-ref --short HEAD) == $version ]] ; then\n git pull\n else\n git -c advice.detachedHead=false checkout $version\n fi\n'", "sudo -H -E -u discourse git config user.discourse-version $version", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p /shared/tmp/{backups,restores}\"", "bash -c \"ln -s /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "[ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete"]} bootstrap failed with exit code 128 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. adc8ef45e9ae880827c9294dbbf73dfe9ab413a050c83fe3f4722c2911876ce2 version只支持分支，不支持标签！正确的应该是 params: version: release/2025.11 根本原因是git symbolic-ref --short HEAD命令只能返回分支名称。如果需要支持标签或者hash需要改成下面的命令 git describe --exact-match --tags 2>/dev/null || git rev-parse --short HEAD 但是，不建议这么改，过多的自定义将导致潜在的技术债。除非官方自己修改。至于我为什么要拉取release/2025.11因为现在生产环境是这个接近的版本，然后我想升级，但是怕出现问题，而且审核流程不允许我直接操作升级，必须先在测试环境验证升级过程（release/2025.11=>release/2026.1）没问题才能在生产环境操作。虽然这有些啰嗦，但是确实是流程正确的最佳选择。于是，我不得不在这里寻找拉取特定分支或标签的方法。抱歉说了这么多废话。幸运的是，现在找到了还算过得去的解决方法。感谢大家。

version: release/2026.1 should work fine. If you want to take advantage of the new overlapping support periods on versions, then this is the correct way to do it. (but of course, you must to remember to update manually before 2026.1 reaches its end-of-life) version: esr should also work. The system is designed to support tags. It is implemented as git checkout $version. [imagem] Singi Qin: Edit templates/web.template.yml You should not make this change in web.template.yml. You should make it in your site-specific containers/app.yml

[imagem] Singi Qin: params: version: release/2026.1 I think it would be very unusual to configure a specific version, rather than a flavour/stream/tag, like latest or stable. I’m actually no longer sure what tags are normal and available and useful with this system.

Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? Maybe it helps for understanding which tags are useful

是的，普通用户使用默认的latest就足够了。但是对应我这种场景来说，不得不研究如何使用特定版本。我总不能对boss说：“哦，很遗憾，Discourse暂时不支持检出特定版本，我们只能更新到最新版。”

这个帖子非常有用，我将仔细看一下。感谢。

[imagem] Moin: Have you taken a look at Configure a supported tracking branch to get Discourse software updates ? I hadn’t seen that - thanks. Looks like we should be using latest/release/esr now. I see my own (old) app.yml picks up the default by being commented out: ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed

version 目前不支持标签，如果要支持，需要修改构建的脚本。本来最佳实践是： params: version: esr 但是目前，不得不修改成 params: version: release/2026.1

Interesting. Even before the new versioning strategy, beta had been a tag instead of a branch for quite a while: Upcoming changes to the beta branch of Discourse

是我，我也很困惑，但是目前的构建代码确实无法使用标签。这本不应该如此。

Something doesn’t appear to be right here. I was running v3.5.0 beta3 with the yml set to version: tests-passed Then I noticed this versioning change so before rebuilding I changed the yml to version: esr and then did a rebuild from the CLI. Now in discourse I see Installed 2026.3.0-latest.1 This appears to be using the tests passed tag instead of the esr tag. I verified that app.yml is showing the version as esr , so why it it grabbing the latest build ?

So essentially there’s no way to get the most recent stable / esr build anymore?

Ajuda para implantar versões mais antigas do Discourse

Suporte ao Produto Instalação

Ed_S (Ed S) Março 28, 2026, 8:07pm 21

Acredito que version deve ser indentado porque faz parte de params.

Tópico		Respostas	Visualizações
How can i rebuild discourse without changing version? Self-hosting	11	2915	5 de Fevereiro de 2021
Unable to make the version of `2.9.0.beta6` running Self-hosting unsupported-install	5	433	16 de Abril de 2024
Shallow git fetch regression in discourse_docker Product Support	15	2578	6 de Janeiro de 2021
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	37	3160	3 de Fevereiro de 2024
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	649	8 de Agosto de 2024

Ajuda para implantar versões mais antigas do Discourse

Tópicos relacionados