Differences

This shows you the differences between two versions of the page.

--- wiki:room_updates [2026/10/02 05:13] – Document v6.7 room updates, quieter chat and database reliability wikiadmin
+++ wiki:room_updates [2026/10/02 06:23] (current) – Document v6.7.2 website, Discord, authentication and update safety fixes wikiadmin
@@ Line 4: / Line 4: @@
 ^ Availability | Compatible room updates after v6.7 adoption |
-^ Documentation status | Upcoming; v6.7.0 queued at review |
+^ Documentation status | Available; all rooms running v6.7.2 on October 1, 2026 |
-^ Behavior reference | v6.7.0 · reviewed 2026-10-01 |
+^ Behavior reference | v6.7.2 · reviewed 2026-10-01 |
 ===== What players will notice =====
-An update waits for the affected room to be empty and idle continuously for at least **30 seconds**. Spectators count as occupants. The bot does not deliberately interrupt a match to install a room update.
+An update waits for the affected room to be empty and idle continuously for at least **30 seconds**. Spectators count as occupants. Players are not kicked or removed to install automatic updates. An occupied room or an unknown roster blocks infrastructure closure.
 When an empty room is replaced, it receives a **new room ID**. Old bookmarks or invites may stop working. Use **Join a lobby** at the top of the site or [[status:start|Live lobbies]] to find its current link. Other rooms keep their players, matches and join links during that individual handoff.
@@ Line 36: / Line 36: @@
 ===== The first v6.7 adoption =====
-The running v6.6 service uses the old architecture, so the initial adoption needs one coordinated restart after **all four** rooms are empty and idle continuously for at least 30 seconds. Independent updates become available after that adoption succeeds. This first handover is queued at the October 1 review; publishing these articles does not deploy the bot.
+The initial v6.7 adoption completed on October 1, 2026 through an operator-approved maintenance restart. All four old rooms were confirmed closed before the new supervisor opened their replacements. Compatible future room updates use the individual empty-and-idle safety window described above. Shared supervisor, protocol, dependency and database changes still need a coordinated upgrade.
 The supervisor keeps shared account connections and coordinates room ownership. Its own version can differ from the workers' compatible versions. The wiki's verified release inventory describes a reviewed release; one account-level version notice does not prove that every room has identical code during a rollout.