Say older Excalidraw clients are refused now, and that NEC-202 is met #334
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!334
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-202-floor-0-5-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NEC-202 asked for the floor to name the first release that syncs Excalidraw drawings structurally. That release was 0.5.0, so the 0.5.2 raise from #333 meets it. Its acceptance also asked that
docs/sync-limitations.mdstop saying older clients' drawing edits are kept as copies until the floor moves.docs/sync-limitations.md, the Excalidraw older-client bullet. Since 30 October the hosted service refuses clients older than 0.5.2 with 4007, and they keep editing locally until they update. A server with no floor set (MIN_PLUGIN_VERSIONdefaults to0) still admits them, so the copy behaviour still applies there.docs/releasing.md. It said NEC-202 was opened for the 0.6.0 raise, which is wrong. It now records the raise as applied and read back: the container'sMIN_PLUGIN_VERSIONprinted 0.5.2, and all 6 connections were back on 0.5.2 within seconds. The 0.6.0 raise gets its own card, not before 27 November.Verified locally:
deployvitest, 223/223, including the floor-wording test.Task: NEC-202
Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B