From 108b15934f1bcb92abc2c820feff2c4f646f0660 Mon Sep 17 00:00:00 2001 From: vorotamoroz Date: Sat, 26 Sep 2026 09:32:30 +0000 Subject: [PATCH] Clarify deferred remediation processing in release notes --- updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/updates.md b/updates.md index 7b5405e9..f1cb1f32 100644 --- a/updates.md +++ b/updates.md @@ -22,7 +22,7 @@ Earlier releases remain available in the 1.0 release history, the 1.0 preview hi - Files with colons in their names now retain their full paths in synchronisation data instead of appearing as incorrectly named copies at the Vault root. (#1206) - Obsidian may refuse to create a missing file with such a name. LiveSync also treats these names as invalid on Windows and Android, so the file may not appear in those devices' Vaults. Existing misplaced copies are left for you to review; this change does not remove them automatically. -- Received changes within the configured modification-time limit are applied to the Vault again while remediation mode is active. Changes newer than the limit remain blocked, and changes arriving during a fetch wait until the local database is usable. +- Received changes within the configured modification-time limit are applied to the Vault again while remediation mode is active. Changes newer than the limit remain blocked; changes arriving while a fetch makes the local database unavailable are kept for a later attempt. - A scheduled fetch no longer offers Simple Fetch while remediation mode is active. This prevents the fetch from bypassing the modification-time limit; the detailed flow explains the restriction and offers to clear it first (#1202). Thank you to @kimjansheden for both fixes and the regression tests in PR #1208! - On start-up, an unchanged file with a missing local revision record can be recognised before newer content arrives, avoiding an unnecessary conflict. Files with actual local edits still require conflict review. (#1207)