📝(changelog) note that get-connections is dropped, not deferred

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 <kevin.jahns@protonmail.com>
This commit is contained in:
Kevin Jahns
2026-09-02 09:36:38 +02:00
committed by Manuel Raynaud
parent 9544915f91
commit 6a5eb379c5
+5 -3
View File
@@ -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