1.0.38
17th October, 2026
This update brings together several improvements to make synchronisation more robust. Among them is a more reliable check for files that have not changed, helping us avoid unnecessary conflicts while protecting local edits. The first file scan after updating may therefore take longer while the plug-in checks existing files and adds content hashes to their local records. Once those records have been updated, later scans skip this extra work.
Synchronisation
Added
- We can opt into NFC path identity for CouchDB synchronisation between the CLI and Obsidian. This prevents decomposed or mixed Unicode file names from becoming inaccessible through a receiving device's normalised path. (#1259)
- Existing Vaults retain their current identity rules. Migration requires updated clients, a Rebuild from a complete authoritative Vault, and a Fetch on the other devices.
- Reconstruction stops when the supported host file listing or local Metadata exposes ambiguous files or parent folders under NFC and the configured case handling. The CLI retains existing physical file names. P2P and Object Storage do not support the new mode.
Fixed
- We can synchronise file deletions and renames when Do not keep metadata of deleted files. is enabled.
- A file restored during the final deletion check remains in the receiving Vault.
- We can resolve configuration mismatches when Encrypt internal file Properties is enabled but its encryption prerequisites are inactive. (#1180)
- Compatible chunk settings can be aligned automatically, or reviewed through
Sync now. Applying those settings preserves our inactive encryption preference.
- Compatible chunk settings can be aligned automatically, or reviewed through
- We can receive synchronised updates to unchanged files even after the local database has discarded their recorded revision, avoiding unnecessary conflicts. (#1207)
- Saved content evidence survives revision-history pruning. Genuine local edits remain protected, and older records are upgraded only after their content is verified.
Maintenance
- The Review Harness can compare SHA-256 and xxHash64 file-content hashing on the current device, with fixed inputs from 4 KiB to 50 MiB and separate initialisation and warm-up measurements.