Differences

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

--- updates:v6_7_0 [2026/10/02 05:13] – Document v6.7 room updates, quieter chat and database reliability wikiadmin
+++ updates:v6_7_0 [2026/10/02 06:23] (current) – Document v6.7.2 website, Discord, authentication and update safety fixes wikiadmin
@@ Line 1: / Line 1: @@
 ====== v6.7.0: Independent room updates and quieter lobbies ======
-**Deployment status (October 1, 2026):** validated and queued. v6.6.22 remains active at this review. The initial v6.7 adoption waits until all four rooms are empty and idle continuously for at least 30 seconds. The website/monitoring database-reader fix described below is already installed. Check [[status:start|Live lobbies]] and [[updates:start|release history]] for subsequent deployment status.
+**Deployment status (October 1, 2026):** deployed; superseded by [[updates:v6_7_2|v6.7.2]], which restores headless chat. The initial adoption completed through an operator-approved maintenance restart, with all old rooms confirmed closed before the four v6.7 lobbies reopened. Compatible future updates can now move through empty rooms independently. Use [[status:start|Live lobbies]] for current join links.
 ===== Independent room updates =====
@@ Line 29: / Line 29: @@
 The website and monitoring readers now access SQLite using the database owner's identity. This operational fix is already live and did not require a bot restart. The new dependency is included in website backups.
-The queued bot changes add bounded retries for connection setup and close failed connections. A failed download-availability cache read uses existing in-memory results and the osu! API path instead of terminating the lobby. Explicit unavailable-map and unavailable-set quarantine stays in force, including forced checks. Application writes are not automatically replayed.
+The deployed bot changes add bounded retries for connection setup and close failed connections. A failed download-availability cache read uses existing in-memory results and the osu! API path instead of terminating the lobby. Explicit unavailable-map and unavailable-set quarantine stays in force, including forced checks. Application writes are not automatically replayed.
 ===== Validation =====