docs: the versioned release exists now, so stop sending users to :next

[LMPrado-DZ23]

v3.8.54 shipped on 2026-09-19 — the first versioned release this fork has ever cut. Until then the README and the Docker guide were right to say only the rolling :next channel existed. They are not right any more, and they were still telling an end user to run a mutable pre-release tag while a stable one sits right there.

What was false

Claim	Where	Reality
":latest and the desktop installers begin to exist when a versioned release is cut; until then every command below uses :next"	README banner	15 installers attached; :latest resolves
":next is the channel this fork publishes today"	README, Docker section	:latest and :3.8.54 publish too
"today they are the only images this fork publishes… :X.Y.Z and :latest appear once a version is released"	README, :next note	they appeared
"only :next and :next-web. No versioned release has been published yet, so :latest, :latest-web and the immutable :X.Y.Z tags are not resolvable"	docs/guides/DOCKER_GUIDE.md — the page the README links to for release channels	all three resolve

What changed

• The "Published right now" banner lists what exists: desktop installers on every Release, :latest and immutable :X.Y.Z, rolling :next / :next-web, and source.
• The four docker run quick-start commands use :latest.
• The mutability warning moved next to the command instead of living only in a later note: :latest is a moving pointer, pin :X.Y.Z for anything reproducible.
• The :next note recommends an immutable tag first, digest second.

Replacing a stale claim with an unverified one would be no better

Every channel in the guide's table was pulled anonymously before the new sentence was written:

latest       HTTP 200      next       HTTP 200
latest-web   HTTP 200      next-web   HTTP 200
3.8.54       HTTP 200      main       HTTP 404
                           main-web   HTTP 404

:main and :main-web do not exist here — this fork develops on release/v* branches, not main — so the note says so outright rather than implying the whole table is pullable.

The ":latest follows the highest published stable SemVer" claim was checked against the workflow, not assumed: docker-publish.yml runs scripts/ci/should-promote-latest.sh against every v* tag and refuses to promote :latest for a pre-release identifier or for anything that is not the highest stable version.

Verification

Isolated DATA_DIR / HOME / USERPROFILE / APPDATA.

Gate	Result
check-docs-sync	exit 0
check-doc-links	exit 0
check-fabricated-docs	exit 0
check-docs-frontmatter	exit 0
check-changelog-integrity	exit 0

Documentation only — no runtime code changes.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 29580a33-dfe8-4263-86cf-355faacb63c7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}