bump

manifest.json

@@ -1,7 +1,7 @@
 {
  "id": "obsidian-livesync",
  "name": "Self-hosted LiveSync",
- "version": "0.23.4",
+ "version": "0.23.5",
  "minAppVersion": "0.9.12",
  "description": "Community implementation of self-hosted livesync. Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
  "author": "vorotamoroz",

package.json

@@ -1,6 +1,6 @@
 {
  "name": "obsidian-livesync",
- "version": "0.23.4",
+ "version": "0.23.5",
  "description": "Reflect your vault changes to some other devices immediately. Please make sure to disable other synchronize solutions to avoid content corruption or duplication.",
  "main": "main.js",
  "type": "module",

updates.md

@@ -18,6 +18,16 @@ I have a lot of respect for that plugin, even though it is sometimes treated as
 Hooray for open source, and generous licences, and the sharing of knowledge by experts.
 
 #### Version history
+- 0.23.5:
+ - New feature:
+ - Now we can check configuration mismatching between clients before synchronisation.
+ - Default: enabled / Preferred: enabled / We can disable this by the `Do not check configuration mismatch before replication` toggle in the `Hatch` pane.
+ - It detects configuration mismatches and prevents synchronisation failures and wasted storage.
+ - Now we can perform remote database compaction from the `Maintenance` pane.
+ - Fixed:
+ - We can detect the bucket could not be reachable.
+ - Note:
+ - Known inexplicable behaviour: Recently, (Maybe while enabling `Incubate chunks in Document` and `Fetch chunks on demand` or some more toggles), our customisation sync data is sometimes corrupted. It will be addressed by the next release.
 - 0.23.4
  - Fixed:
  - No longer experimental configuration is shown on the Minimal Setup.