Skip to content

1.0.0-beta.3

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Jul 12:12

1.0.0-beta.3

24th July, 2026

The work towards 1.0 has become so substantial that I have written an article about it.

I hope this will let us move on to the next phase.

These notes consolidate the changes introduced from 1.0.0-beta.1 through 1.0.0-beta.3 and describe the behaviour present in beta.3.

Important

  • This remains an opt-in integration preview and does not replace the latest stable release. Update every participating device before resuming synchronisation, and continue to use a current backup while testing with an existing Vault.

Improved

  • Choosing Not now on a merge conflict now postpones repeated dialogues for that conflict while the active file retains an unresolved-conflict warning. Three or more live versions show their current count and are reviewed one deterministic pair at a time; completed pairs remain resolved across restart. The existing conflict commands can reopen a postponed conflict explicitly, and a later conflict prompts again after the current one has been resolved.
  • Enabling Hidden File Sync now opens one progress Notice before its setting is saved and reuses that Notice throughout the initial file scan, instead of stacking separate phase and restart Notices.
  • P2P is now presented only after it has been configured: its status pane no longer opens at start-up, its ribbon icon remains hidden for CouchDB-only Vaults, and the retired P2P pane command has been removed. The current pane distinguishes announcing changes, following a peer, and persistent per-device actions. Setup and guidance now distinguish the required signalling relay from optional TURN, and describe the public signalling relay's privacy and availability limits.
  • First-device P2P setup now accepts a successfully opened signalling room without requiring another peer to be online. Additional-device Fetch still requires selecting a source peer and completing P2P Rebuild.
  • Manual CouchDB setup now distinguishes creating a first database from connecting an additional device to an existing one. Settings mode can save an unverified profile explicitly, while onboarding requires a successful connection, and each proposed server-configuration fix requires separate confirmation.
  • Differences limited to the chunk hash algorithm, chunk size, or splitter version are now aligned automatically by default. Existing content remains readable, while an explicit opt-out and any difference which also involves an incompatible setting retain manual review.

Fixed

  • Conflict resolutions made on another device no longer recreate the same conflict when the receiving Vault still contains the exact content of the deleted losing revision. Automatic text and structured-data merge now uses the nearest revision actually shared by both branches instead of inferring ancestry from revision generation numbers.
  • Edits, deletions, and renames made while a file is conflicted now extend the exact revision displayed on that device. If LiveSync cannot prove the displayed branch, it preserves the affected branches for review instead of silently applying the operation to the database winner.
  • Answering or externally closing a merge dialogue immediately no longer leaves conflict processing waiting for a response which has already occurred.
  • Choosing Apply settings to this device, and fetch again for a compatible configuration mismatch now applies the remote settings before Fetch, instead of updating the remote database with this device's settings.
  • Accepted settings which control how new chunks are created now take effect before synchronisation is retried, rather than leaving the previous hash or splitter active until restart.

Testing

  • Added revision-tree regressions and focused real-Obsidian scenarios for propagated conflict resolutions, file operations performed while a conflict remains active, multiple-version review, and restart between resolution stages.
  • Added regressions for P2P configuration, the distinction between setting up the first device and using Fetch on an additional device, the P2P status pane, CouchDB setup policy, and mobile dialogues.