bump

manifest.json

@@ -1,7 +1,7 @@
 {
     "id": "obsidian-livesync",
     "name": "Self-hosted LiveSync",
-    "version": "0.23.15",
+    "version": "0.23.16",
     "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-lock.json

@@ -1,12 +1,12 @@
 {
     "name": "obsidian-livesync",
-    "version": "0.23.14",
+    "version": "0.23.16",
     "lockfileVersion": 2,
     "requires": true,
     "packages": {
         "": {
             "name": "obsidian-livesync",
-            "version": "0.23.14",
+            "version": "0.23.16",
             "license": "MIT",
             "dependencies": {
                 "@aws-sdk/client-s3": "^3.556.0",

package.json

@@ -1,6 +1,6 @@
 {
     "name": "obsidian-livesync",
-    "version": "0.23.14",
+    "version": "0.23.16",
     "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,12 @@ 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.16:
+  - Maintenance Update:
+    - Library refining (Phase 1 - step 2). There are no significant changes on the user side.
+    - Including the following fixes of potentially problems:
+      - the problem which the path had been obfuscating twice has been resolved.
+      - Note: Potential problems of the library; which has not happened in Self-hosted LiveSync for some reasons.
 - 0.23.15:
   - Maintenance Update:
     - Library refining (Phase 1). There are no significant changes on the user side.