Releases: vrtmrz/obsidian-livesync
0.25.38
0.25.37
0.25.37
15th January, 2026
Thank you for your patience until my return!
This release contains minor changes discovered and fixed during test implementation.
There are no changes affecting usage. Just for minimise differences and simplify subsequent releases or merges.
Refactored
- Logging system has been slightly refactored to improve maintainability.
- Some import statements have been unified.
0.25.36
0.25.36
25th December, 2025
I am feeling a little relieved now that it has finally reached a stable, usable garbage collector.
That said, it is still in beta. Please let me know if you encounter any problems, and please make sure your backup!
Improved
- Now the garbage collector (V3) has been implemented. (Beta)
- This garbage collector ensures that all devices are synchronised to the latest progress to prevent inconsistencies.
- In other words, it makes sure that no new conflicts would have arisen.
- This feature requires additional information (via node information), but it should be more reliable.
- This feature requires all devices have v0.25.36 or later.
- After the garbage collector runs, the database size may be reduced (Compaction will be run automatically after GC).
- We should have an administrative privilege on the remote database to run this garbage collector.
- Now the plug-in and device information is stored in the remote database.
- This information is used for the garbage collector (V3).
- Some additional features may be added in the future using this information.
0.25.35
0.25.35
24th December, 2025
Sorry for a small release! I would like to keep things moving along like this if possible. After all, the holidays seem to be starting soon. I will be doubled by my business until the 27th though, indeed.
Fixed
- Now the conflict resolution dialogue shows correctly which device only has older APIs (#764).
0.25.34
0.25.34
10th December, 2025
Behaviour change
- The plug-in automatically fetches the missing chunks even if
Fetch chunks on demandis disabled.- This change is to avoid loss of data when receiving a bulk of revisions.
- This can be prevented by enabling
Use Only Local Chunksin the settings.
- Storage application now saved during each event and restored on startup.
- Synchronisation result application is also now saved during each event and restored on startup.
- These may avoid some unexpected loss of data when the editor crashes.
Fixed
- Now the plug-in waits for the application of pended batch changes before the synchronisation starts.
- This may avoid some unexpected loss or unexpected conflicts.
- Plug-in sends custom headers correctly when RequestAPI is used.
- No longer causing unexpected chunk creation during
Reset synchronisation on This Devicewith bucket sync.
Refactored
- Synchronisation result application process has been refactored.
- Storage application process has been refactored.
- Please report if you find any unexpected behaviour after this update. A bit of large refactoring.
0.25.33
0.25.33
05th December, 2025
New feature
- We can analyse the local database with the
Analyse database usagecommand.- This command makes a TSV-style report of the database usage, which can be pasted into spreadsheet applications.
- The report contains the number of unique chunks and shared chunks for each document revision.
- Unique chunks indicate the actual consumption.
- Shared chunks indicate the reference counts from other chunks with no consumption.
- We can find which notes or files are using large amounts of storage in the database. Or which notes cannot share chunks effectively.
- This command is useful when optimising the database size or investigating an unexpectedly large database size.
- The report contains the number of unique chunks and shared chunks for each document revision.
- This command makes a TSV-style report of the database usage, which can be pasted into spreadsheet applications.
- We can reset the notification threshold and check the remote usage at once with the
Reset notification threshold and check the remote database usagecommand. - Commands are available from the Command Palette, or
Hatchpane in the settings dialogue.
Fixed
- Now the plug-in resets the remote size notification threshold after rebuild.
0.25.32
0.25.32
02nd December, 2025
Now I am back from a short (?) break! Thank you all for your patience. (It is nothing major, but the first half of the year has finally come to an end).
Anyway, I will release the things a bit by bit. I think that we need a rehabilitation or getting gears in again.
Improved
- Now the plugin warns when we are in several file-related situations that may cause unexpected behaviour (#300).
- These errors are displayed alongside issues such as file size exceeding limits.
- Such situations include:
- When the document has a name which is not supported by some file systems.
- When the vault has the same file names with different letter cases.
0.25.31
0.25.30-dev
0.25.30-dev
17th November, 2025
So sorry for the quick follow-up release, due to a humble mistake in a quick causing a matter.
Fixed
- Now we can save settings correctly again (#756).