v1.64.1

Fixed

• Removed the topbar "Suggestions" button — it opened nothing (there is no separate suggestions panel; suggestions live in the comments rail). Its pending-suggestion count now folds into the comments button's badge, which counts unresolved comments plus pending suggestions together.

Full Changelog: v1.64.0...v1.64.1

v1.64.0

Changed

• Several small tracked-change suggestions on one source line now group into a single annotation-rail card with a row per change — each row and the whole group have their own accept / reject. A suggestion with an open reply thread stays on its own card.

Full Changelog: v1.63.0...v1.64.0

v1.63.0

Added

• Anonymous collaborators on a shared link each get a stable, distinct identity and a guest name (e.g. "Quiet Lynx"). Their suggestions, comments, edits in version history, and presence cursor are all attributed to that one guest instead of a shared "Anonymous", and the guest identity survives a page reload.

Fixed

• An anonymous reviewer can now withdraw their own pending suggestion — the Withdraw button was never appearing for them.

Full Changelog: v1.62.12...v1.63.0

v1.62.12

Fixed

• Renaming a shared document no longer drops the comments and tracked-change suggestions in the other shared documents that link to it. The server rewrites each [[Old Name]] reference in place now, instead of replacing the whole document body — so anchors elsewhere in those documents stay put.

Full Changelog: v1.62.11...v1.62.12

v1.62.11

Fixed

• Security fixes from a follow-up external audit:
  • Only an editor can add a new document to a shared workspace. A viewer or reviewer on an "anyone with the link" workspace could previously make the collaboration server register arbitrary document ids just by asking to sync them — cluttering the workspace and, in bulk, slowing its next restart.
  • The rel="noopener noreferrer" hardening applied to raw <a target="_blank"> links in a document now also catches uppercase variants (target="_BLANK", rel="OPENER") and links inside inline SVG.

Full Changelog: v1.62.10...v1.62.11

v1.62.10

Fixed

• The Command Palette could get stuck invisible if you pressed Escape in the instant right after opening it (before its search box took focus) — its close is now handled the same way as every other dialog.

Full Changelog: v1.62.9...v1.62.10

v1.62.9

Fixed

• Security hardening from a follow-up external audit:
  • Asking where a migrated legacy document went now requires access to that document — previously an unauthenticated request could learn the workspace id (and from there the document's title) if it already knew the old link.
  • A raw HTML <a target="_blank"> typed into a document's markdown always gets rel="noopener noreferrer" now, matching the app's own generated links.
  • Citation keys are HTML-escaped where they're placed into link/id attributes.

Full Changelog: v1.62.8...v1.62.9

v1.62.8

Changed

• The legacy single-document collaboration rooms (superseded by workspaces long ago) are now a thin migration shim: opening an old share link still moves the document into a workspace exactly as before, but the retired room no longer runs any live-editing, version-history or comment code at all — closing the surface that several audit rounds kept finding gaps in.

Full Changelog: v1.62.7...v1.62.8

v1.62.7

Fixed

• Security hardening for the legacy single-document collaboration rooms (superseded by workspaces), from a follow-up external audit — the same three fixes already applied to the modern rooms:
  • A frame from a socket the server no longer recognises is dropped, not applied.
  • Once a legacy document has been migrated into a workspace, the old room turns every request away and disconnects anyone still on it, so edits can't be stranded in a dead copy.
  • Changing who can access a legacy document now takes effect on already-connected sessions immediately.

Full Changelog: v1.62.6...v1.62.7

v1.62.6

Fixed

• More collaboration-layer security hardening from a follow-up external audit:
  • A collaborator whose access was just revoked can no longer land a last write on the shared document by racing the connection close — a frame from a socket the server no longer recognises is dropped.
  • Restoring a version can no longer write document history back into storage moments after the workspace was deleted.
  • A WebSocket that finishes connecting just after the workspace is deleted is now turned away instead of joining a dead room.
  • A "request edit access" note and the requester's name are now sent only to the owner's own session, not broadcast to every connected collaborator.

Full Changelog: v1.62.5...v1.62.6