From 25173180d72d79e633e9e9dde8d3dfe3b8900d09 Mon Sep 17 00:00:00 2001 From: vorotamoroz Date: Sat, 26 Sep 2026 09:25:13 +0000 Subject: [PATCH] Clarify 1.0.31 remediation notes --- updates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/updates.md b/updates.md index b5d0199d..7b5405e9 100644 --- a/updates.md +++ b/updates.md @@ -22,8 +22,8 @@ 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 are applied again while remediation mode is active. That mode prevents the scan which readiness depends upon, so nothing had been applied since the plug-in began waiting for readiness, not even changes older than the configured modification-time limit. The limit itself is still enforced for every change, and application waits for a usable local database so that a change arriving during a fetch is not dropped. -- A scheduled fetch no longer offers Simple Fetch while remediation mode is active. Simple Fetch reconciles the Vault with the local database past the restriction, which could store the current files or apply changes newer than the limit; the detailed flow states the restriction and offers to clear it first (#1202). Thank you to @kimjansheden for both fixes and the regression tests in PR #1208! +- 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. +- 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) ## 1.0.30