From 6a5eb379c51ba125844ff149671d7c8a0aa79608 Mon Sep 17 00:00:00 2001 From: Kevin Jahns Date: Thu, 6 Aug 2026 09:29:04 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D(changelog)=20note=20that=20get-con?= =?UTF-8?q?nections=20is=20dropped,=20not=20deferred?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The hocuspocus-to-yhub migration entry claimed both the kick and get-connections APIs were deferred pending a yhub equivalent. The kick flow now has its server-side replacement (the reset-connections endpoint, backend wiring pending), and get-connections lost its only consumer when the can-edit mechanism was removed — it is dropped, not awaiting reimplementation. Signed-off-by: Kevin Jahns --- CHANGELOG.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 22d65c60e..55206086f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -265,9 +265,11 @@ and this project adheres to - 🐛(keycloak) fix database env variables in the self-hosting example #2572 - 🐛(helm) show the database error while jobs wait for it to be ready #2578 - ♻️(collaboration) migrate the collaboration server from hocuspocus to yhub: - the dev stack gains dedicated valkey and postgres services for yhub, and - the kick (reset-connections) and get-connections APIs have no yhub - equivalent yet — they are deferred with TODO(yhub) stubs + the dev stack gains dedicated valkey and postgres services for yhub. The + kick flow is deferred with TODO(yhub) stubs (the reset-connections + endpoint added above is its server-side replacement, backend wiring + pending). The get-connections API is dropped for good: its only consumer + was the removed can-edit mechanism, so it is not needed anymore - 🔥(backend) remove the unused `CollaborationService` - 💥(backend) remove the `documents/{id}/can-edit/` endpoint - 💥(y-provider) the published `lasuite/impress-y-provider` image becomes