Say older Excalidraw clients are refused now, and that NEC-202 is met #334

Merged
cruelacid merged 1 commit from worktree-nec-202-floor-0-5-2 into main 2026-10-30 23:36:25 +00:00
Owner

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.md stop 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_VERSION defaults to 0) 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's MIN_PLUGIN_VERSION printed 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: deploy vitest, 223/223, including the floor-wording test.

Task: NEC-202

Changelog

NONE

🤖 Generated with Claude Code

https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B

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.md` stop 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_VERSION` defaults to `0`) 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's `MIN_PLUGIN_VERSION` printed 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: `deploy` vitest, 223/223, including the floor-wording test. Task: NEC-202 ## Changelog NONE 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B
Say older Excalidraw clients are refused now, and that NEC-202 is met
All checks were successful
Release note / release-note (pull_request) Successful in 27s
CI / build (pull_request) Successful in 6m57s
CI / e2e (pull_request) Successful in 15m11s
CI / promote (pull_request) Has been skipped
CI / build (push) Successful in 9m17s
CI / e2e (push) Successful in 15m12s
CI / promote (push) Successful in 32s
470c0bdd90
NEC-202 asked for the floor to name the first release that syncs
Excalidraw drawings structurally. That was 0.5.0, so the 0.5.2 raise
meets it, and its acceptance asks that sync-limitations.md stop
describing older clients' drawing edits as copied until the floor
moves. On the hosted service they are now refused with 4007; a server
with no floor set still admits them, and the copy behaviour holds there.

releasing.md also said NEC-202 was opened for the 0.6.0 raise, which it
was not, and now records the raise as applied and read back.

Task: NEC-202

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!334
No description provided.