Archive published 1.0.43 release notes

docs/releases/1.0.md

@@ -2,6 +2,63 @@
 
 This document contains earlier published releases from the 1.0 line of the [current Self-hosted LiveSync release history](../../updates.md). Beta and release-candidate builds published before 1.0.0 are recorded in the [1.0 preview history](1.0-previews.md). Earlier release lines continue in the [0.25 history](0.25.md) and the [legacy history](legacy.md).
 
+## 1.0.43
+
+30th October, 2026
+
+### Synchronisation
+
+#### New Feature
+
+- We can avoid accidentally editing out-of-date notes while a large CouchDB catch-up is in progress. (#1241, #1275)
+    - Turn on **Enable SyncGuard** under **General Settings** → **Appearance** to cover the workspace until incoming changes have been received and applied to the Vault.
+    - Disabled by default. During CouchDB LiveSync mode start-up or resume, protection begins after a configurable number of distinct incoming notes is detected (default: 20).
+    - **Continue without waiting** releases the workspace, including after a failed or interrupted transfer. Synchronisation can continue, and some notes may still be out of date.
+    - The settings apply only to this device.
+    - Small catch-up transfers and ordinary live changes remain uninterrupted. Some changes can arrive before the guard activates; it does not prevent other plug-ins or external tools from editing files.
+
+#### Improved
+
+- We can tell that CouchDB synchronisation is progressing while it compares existing revisions, even before any files are uploaded. (#1293, #1294)
+    - Separate `⏩↑` and `⏩↓` counts show the change-feed entries compared for push and pull. These are comparison counts; the upload and download totals remain separate.
+    - Existing CSS snippets which target `livesync-stat-ff` to hide comparison progress need to target both `livesync-stat-ff-push` and `livesync-stat-ff-pull`. The status display guide includes updated examples.
+
+### Setup and recovery
+
+#### Fixed
+
+- We can choose how a new Join or scheduled Fetch handles our existing files, without silently reusing choices from an earlier Fetch. (#1244, #1296)
+    - Each new operation asks again, including after a previous Fetch changed the local database suffix. Fast Setup retains interrupted choices in an editable code block in the fetch flag.
+    - On restart, we confirm the current remote and saved choices, choose again, or cancel; a remaining flag never reapplies choices silently.
+    - If the saved selection cannot be read, we can choose new options for that attempt without repairing or rewriting the flag. Completing or cancelling the operation removes the whole flag.
+    - After updating during an interrupted Fetch, confirm the choices once more. Older separately stored choices are ignored; downloaded data and the existing checkpoint are not removed by this change.
+
+### Dialogues
+
+#### Fixed
+
+- Confirmation and setup actions are easier to follow, and keyboard focus remains visible. (#1297)
+    - Buttons align with the content above them, with room for confirmation buttons' focus outlines.
+- Mobile dialogues retain Obsidian's standard spacing and leave more usable space above the software keyboard. (#1297)
+
+### Translations
+
+- More settings, setup, recovery, and configuration messages are available in Simplified Chinese. (#1258)
+    - Expanded the translation catalogue to include previously untranslated messages and shared-library labels.
+
+### Miscellaneous
+
+- Docker setup now handles shell-sensitive characters in health-check credentials correctly, avoiding false authentication failures which could prevent CouchDB initialisation. (#1295)
+
+### Acknowledgements
+
+Thank you for your contributions!
+
+- @Akilaydin, for adding the optional SyncGuard workspace protection (#1275).
+- @ARCJ137442, for adding separate push and pull comparison progress displays (#1294).
+- @Jovlang, for correcting Docker health-check credential quoting and authenticated readiness checks (#1295).
+- @kannazuki-c, for expanding the Simplified Chinese translations (#1258).
+
 ## 1.0.42
 
 27th October, 2026

updates.md

@@ -258,60 +258,3 @@ Please let me know if any problems arise from these changes.
 Thank you for your contributions!
 
 - @AdrianNicu, for improving decryption handling during database initialisation (Commonlib #191).
-
-## 1.0.43
-
-30th October, 2026
-
-### Synchronisation
-
-#### New Feature
-
-- We can avoid accidentally editing out-of-date notes while a large CouchDB catch-up is in progress. (#1241, #1275)
-    - Turn on **Enable SyncGuard** under **General Settings** → **Appearance** to cover the workspace until incoming changes have been received and applied to the Vault.
-    - Disabled by default. During CouchDB LiveSync mode start-up or resume, protection begins after a configurable number of distinct incoming notes is detected (default: 20).
-    - **Continue without waiting** releases the workspace, including after a failed or interrupted transfer. Synchronisation can continue, and some notes may still be out of date.
-    - The settings apply only to this device.
-    - Small catch-up transfers and ordinary live changes remain uninterrupted. Some changes can arrive before the guard activates; it does not prevent other plug-ins or external tools from editing files.
-
-#### Improved
-
-- We can tell that CouchDB synchronisation is progressing while it compares existing revisions, even before any files are uploaded. (#1293, #1294)
-    - Separate `⏩↑` and `⏩↓` counts show the change-feed entries compared for push and pull. These are comparison counts; the upload and download totals remain separate.
-    - Existing CSS snippets which target `livesync-stat-ff` to hide comparison progress need to target both `livesync-stat-ff-push` and `livesync-stat-ff-pull`. The status display guide includes updated examples.
-
-### Setup and recovery
-
-#### Fixed
-
-- We can choose how a new Join or scheduled Fetch handles our existing files, without silently reusing choices from an earlier Fetch. (#1244, #1296)
-    - Each new operation asks again, including after a previous Fetch changed the local database suffix. Fast Setup retains interrupted choices in an editable code block in the fetch flag.
-    - On restart, we confirm the current remote and saved choices, choose again, or cancel; a remaining flag never reapplies choices silently.
-    - If the saved selection cannot be read, we can choose new options for that attempt without repairing or rewriting the flag. Completing or cancelling the operation removes the whole flag.
-    - After updating during an interrupted Fetch, confirm the choices once more. Older separately stored choices are ignored; downloaded data and the existing checkpoint are not removed by this change.
-
-### Dialogues
-
-#### Fixed
-
-- Confirmation and setup actions are easier to follow, and keyboard focus remains visible. (#1297)
-    - Buttons align with the content above them, with room for confirmation buttons' focus outlines.
-- Mobile dialogues retain Obsidian's standard spacing and leave more usable space above the software keyboard. (#1297)
-
-### Translations
-
-- More settings, setup, recovery, and configuration messages are available in Simplified Chinese. (#1258)
-    - Expanded the translation catalogue to include previously untranslated messages and shared-library labels.
-
-### Miscellaneous
-
-- Docker setup now handles shell-sensitive characters in health-check credentials correctly, avoiding false authentication failures which could prevent CouchDB initialisation. (#1295)
-
-### Acknowledgements
-
-Thank you for your contributions!
-
-- @Akilaydin, for adding the optional SyncGuard workspace protection (#1275).
-- @ARCJ137442, for adding separate push and pull comparison progress displays (#1294).
-- @Jovlang, for correcting Docker health-check credential quoting and authenticated readiness checks (#1295).
-- @kannazuki-c, for expanding the Simplified Chinese translations (#1258).