Back to the changelog

v0.62.0

July 22, 2026

Process maps no longer lose work and protect published versions. Edits made during a save are no longer overwritten, back-to-back saves no longer trigger false conflicts, and a published map is now truly immutable.

  • Improvement

    Edits made during a save are no longer lost

    If you keep editing the map while a save is in progress, those edits now stay — before they were wiped when the map reloaded. Also, saving twice in a row no longer triggers a false version-conflict warning with yourself.

  • Improvement

    Applying a proposal is safer

    Applying a proposal (BPMN-Lite or Copilot) now preserves the configuration of existing links — it no longer clears mode and event name — and, if the save fails, the preview stays open with the map unchanged instead of showing a never-saved version.

  • Security

    Published versions protected and concurrency enforced

    A published map is now immutable in its metadata too: name, description, owner and category can no longer be changed on a published version (a new version is required). And concurrent-edit protection is enforced server-side: an edit based on a stale version is always rejected, even from scripts or external integrations.

  • Improvement

    Map designer refinements

    Export now warns you if there are unsaved changes before downloading the last saved version; the "Simulation" and "AI Analysis" panels no longer overlap (opening one closes the other); and a search bar lets you find a map by name in the list.