diff --git a/manifest.json b/manifest.json index baddcdb..1b214ce 100644 --- a/manifest.json +++ b/manifest.json @@ -1,7 +1,7 @@ { "id": "obsidian-livesync", "name": "Self-hosted LiveSync", - "version": "0.25.19", + "version": "0.25.20", "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", diff --git a/package-lock.json b/package-lock.json index e1b8997..6b88f4a 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "obsidian-livesync", - "version": "0.25.19", + "version": "0.25.20", "lockfileVersion": 2, "requires": true, "packages": { "": { "name": "obsidian-livesync", - "version": "0.25.19", + "version": "0.25.20", "license": "MIT", "dependencies": { "@aws-sdk/client-s3": "^3.808.0", diff --git a/package.json b/package.json index d50f3fe..5015f3f 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "obsidian-livesync", - "version": "0.25.19", + "version": "0.25.20", "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", diff --git a/updates.md b/updates.md index 7d2dac7..f306777 100644 --- a/updates.md +++ b/updates.md @@ -8,6 +8,22 @@ I have now rewritten the E2EE code to be more robust and easier to understand. I As a result, this is the first time in a while that forward compatibility has been broken. We have also taken the opportunity to change all metadata to use encryption rather than obfuscation. Furthermore, the `Dynamic Iteration Count` setting is now redundant and has been moved to the `Patches` pane in the settings. Thanks to Rabin-Karp, the eden setting is also no longer necessary and has been relocated accordingly. Therefore, v0.25.0 represents a legitimate and correct evolution. +## 0.25.20 + +26th September, 2025 + +### Fixed + +- Chunk fetching no longer reports errors when the fetched chunk could not be saved (#710). + - Just using the fetched chunk temporarily. +- Chunk fetching reports errors when the fetched chunk is surely corrupted (#710, #712). +- It no longer detects files that the plug-in has modified. + - It may reduce unnecessary file comparisons and unexpected file states. + +### Improved + +- Now checking the remote database configuration respecting the CouchDB version (#714). + ## 0.25.19 18th September, 2025 @@ -78,21 +94,5 @@ As a result, this is the first time in a while that forward compatibility has be - Now informs us about conflicted files as non-recoverable, but noted so. - No longer errors on not-found files. -## 0.25.13 - -1st September, 2025 - -### Fixed - -- Conflict resolving dialogue now properly displays the changeset name instead of A or B (#691). - -## 0.25.12 - -29th August, 2025 - -### Fixed - -- Fixed an issue with automatic synchronisation starting (#702). - Older notes are in [updates_old.md](https://github.com/vrtmrz/obsidian-livesync/blob/main/updates_old.md). diff --git a/updates_old.md b/updates_old.md index 69eecb6..fd9ef6d 100644 --- a/updates_old.md +++ b/updates_old.md @@ -10,6 +10,22 @@ As a result, this is the first time in a while that forward compatibility has be --- +## 0.25.13 + +1st September, 2025 + +### Fixed + +- Conflict resolving dialogue now properly displays the changeset name instead of A or B (#691). + +## 0.25.12 + +29th August, 2025 + +### Fixed + +- Fixed an issue with automatic synchronisation starting (#702). + ## 0.25.11 28th August, 2025 @@ -20,7 +36,6 @@ As a result, this is the first time in a while that forward compatibility has be - No errors are shown during synchronisations in offline (if not explicitly requested) (#699). - Missing some checking during automatic-synchronisation now works correctly. - ## 0.25.10 26th August, 2025 @@ -109,7 +124,6 @@ In next version, insecure chunk detection will be implemented. - Files prefixed `bgWorker.` are now also controls these worker threads. (I know what you want to say... I will rename them). - Removed unused code. - ## ~~0.25.5~~ 0.25.6 (0.25.5 has been withdrawn due to a bug in the `Fetch chunks on demand` feature). @@ -210,7 +224,6 @@ The PBKDF2Salt will be referred to as the `Security Seed`, and it is used to der - The Set-up URI is now encrypted with a new encryption algorithm (mostly the same as `V2`). - The new Set-up URI is not compatible with version 0.24.x or earlier. - ## 0.25.0 ### Fixed @@ -428,7 +441,6 @@ However, just to whisper, this is tremendously fast. - Dependent libraries have been updated to the latest version. - Some build processes have been separated to `pre` and `post` processes. - ## 0.24.25 22nd April, 2025 @@ -506,8 +518,8 @@ However, just to whisper, this is tremendously fast. - No longer conflicted files are handled in the boot-up process. No more unexpected overwriting. - - It ignores `Always overwrite with a newer file`, and always be prevented for - the safety. Please pick it manually or open the file. + - It ignores `Always overwrite with a newer file`, and always be prevented for + the safety. Please pick it manually or open the file. - Some log messages on conflict resolution has been corrected. - Automatic merge notifications, displayed on the grounds of `same`, have been degraded to logs. @@ -516,8 +528,8 @@ However, just to whisper, this is tremendously fast. - Now we can fetch the remote database with keeping local files completely intact. - - In new option, all files are stored into the local database before the - fetching, and will be merged automatically or detected as conflicts. + - In new option, all files are stored into the local database before the + fetching, and will be merged automatically or detected as conflicts. - The dialogue presenting options when performing `Fetch` are now more informative. @@ -539,8 +551,8 @@ However, just to whisper, this is tremendously fast. - **NOW INDEED AND ACTUALLY** `Compute revisions for chunks` are backed into enabled again. it is necessary for garbage collection of chunks. - - As far as existing users are concerned, this will not automatically change, - but the Doctor will inform us. + - As far as existing users are concerned, this will not automatically change, + but the Doctor will inform us. ## 0.24.19 @@ -581,7 +593,6 @@ Confession. I got the default values wrong. So scary and sorry. ## 0.24.16 - ### Improved #### Peer-to-Peer @@ -662,7 +673,6 @@ Sorry for the lack of replies. The ones that were not good are popping up, so I - Displaying replication status of the peer-to-peer synchronisation is separated from the main-log-logic. - Some file names have been changed to be more consistent. - ## 0.24.12 I created a SPA called [webpeer](https://github.com/vrtmrz/livesync-commonlib/tree/main/apps/webpeer) (well, right... I will think of a name again), which replaces the server when using Peer-to-Peer synchronisation. This is a pseudo-client that appears to other devices as if it were one of the clients. . As with the client, it receives and sends data without storing it as a file. @@ -678,7 +688,6 @@ And, this is just a single web page, without any server-side code. It is a stati - And you can see the actual usage of this on [webpeer](https://github.com/vrtmrz/livesync-commonlib/tree/main/apps/webpeer) that a pseudo client for peer-to-peer synchronisation. - Some UIs have been got isomorphic among Obsidian and web applications (for `webpeer`). - ## 0.24.11 Peer-to-peer synchronisation has been implemented!