Table of Contents
v7.1.20 — room update retries and player names
Published October 19, 2026 UTC: release notes and downloads.
What changed
- A healthy room that is not ready to prepare an update keeps its queued target. The controller discards only the unused candidate and retries after another continuous empty interval, with bounded backoff.
- A player joining during preparation postpones the update before room changes. Cancelling the update still works.
- Join greetings use locally known player names immediately. Background profile reads can supply a name before optional score lookups finish. Late results for departed players or old rooms are ignored, and greetings remain once per join.
- Uncertain API outcomes, ownership problems and failed cleanup retain their existing recovery checks.
Installation and rollout
This is a shared-controller update: every configured room on a host must be empty together once. Compatible worker-only updates after it can still roll independently when individual rooms empty. Occupied rooms are not forcibly restarted.
The signed pilot feed supports the exact published v7.1.16 and v7.1.19 baselines. A host with an older pending transition may finish that transition first. Existing configuration, authorization, Discord, catalogs, enrollment, sharing choices, statistics, ratings and boot preferences are preserved. No database migration or dependency change is included.
Keep the existing installation and state; no reinstall, sign-in or repeated ownership-clear is needed for a healthy supported upgrade. A published release is not proof that a particular host has activated it.
Validation
228 affected tests passed. Protected installed tests used full catalogs for owner v7.1.19 → v7.1.20 and community v7.1.16 → v7.1.20 upgrades. A separate disposable worker-update test verified that an occupied sibling stayed running and a temporary preparation refusal retried to completion. That test successor was not a published release.
Unrelated full suites and actual osu! gameplay were not repeated for this qualification. See the release's VALIDATION.json for evidence and limits.