Files
obsidian-livesync/updates.md
vorotamoroz b0c1d6a1bf bump
2025-12-10 09:48:25 +00:00

6.7 KiB

0.25

Since 19th July, 2025 (beta1 in 0.25.0-beta1, 13th July, 2025)

The head note of 0.25 is now in updates_old.md. Because 0.25 got a lot of updates, thankfully, compatibility is kept and we do not need breaking changes! In other words, when get enough stabled. The next version will be v1.0.0. Even though it my hope.

0.25.34

10th December, 2025

Behaviour change

  • The plug-in automatically fetches the missing chunks even if Fetch chunks on demand is disabled.
    • This change is to avoid loss of data when receiving a bulk of revisions.
    • This can be prevented by enabling Use Only Local Chunks in 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 Device with 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

05th December, 2025

New feature

  • We can analyse the local database with the Analyse database usage command.
    • 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.
  • We can reset the notification threshold and check the remote usage at once with the Reset notification threshold and check the remote database usage command.
  • Commands are available from the Command Palette, or Hatch pane in the settings dialogue.

Fixed

  • Now the plug-in resets the remote size notification threshold after rebuild.

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

18th November, 2025

Fixed

  • Now fetching configuration from the server can handle the empty remote correctly (reported on #756).
  • No longer asking to switch adapters during rebuilding.

0.25.30

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).

0.25.28 0.25.29

(0.25.28 was skipped due to a packaging issue.)

17th November, 2025

New feature

  • We can now configure hidden file synchronisation to always overwrite with the latest version (#579).

Fixed

  • Timing dependency issues during initialisation have been mitigated (#714)

Improved

  • Error logs now contain stack-traces for better inspection.

0.25.27

12th November, 2025

Improved

  • Now we can switch the database adapter between IndexedDB and IDB without rebuilding (#747).
    • Just a local migration will be required, but faster than a full rebuild.
  • No longer checking for the adapter by Doctor.

Changes

  • The default adapter is reverted to IDB to avoid memory leaks (#747).

Fixed (?)

  • Reverted QR code library to v1.4.4 (To make sure #752).

0.25.26

07th November, 2025

Improved

  • Some JWT notes have been added to the setting dialogue (#742).

Fixed

  • No longer wrong values encoded into the QR code.
  • We can acknowledge why the QR codes have not been generated.
    • Probably too large a dataset to encode. When this happens, please consider using Setup-URI via text instead of QR code, or reduce the settings temporarily.

Refactored

  • Some dependencies have been updated.
  • Internal functions have been modularised into octagonal-wheels packages and are well tested.
    • dataobject/Computed for caching computed values.
    • encodeAnyArray/decodeAnyArray for encoding and decoding any array-like data into compact strings (#729).
  • Fixed importing from the parent project in library codes. (#729).

0.25.25

06th November, 2025

Fixed

JWT Authentication

  • Now we can use JWT Authentication ES512 correctly (#742).
  • Several misdirections in the Setting dialogues have been fixed (i.e., seconds and minutes confusion...).
  • The key area in the Setting dialogue has been enlarged and accepts newlines correctly.
  • Caching of JWT tokens now works correctly
    • Tokens are now cached and reused until they expire.
    • They will be kept until 10% of the expiration duration is remaining or 10 seconds, whichever is longer (but at a maximum of 1 minute).
  • JWT settings are now correctly displayed on the Setting dialogue.

And, tips about JWT Authentication on CouchDB have been added to the documentation (docs/tips/jwt-on-couchdb.md).

Other fixes

  • Receiving non-latest revisions no longer causes unexpected overwrites.
    • On receiving revisions that made conflicting changes, we are still able to handle them.

Improved

  • No longer duplicated message notifications are shown when a connection to the remote server fails.
    • Instead, a single notification is shown, and it will be kept on the notification area inside the editor until the situation is resolved.
  • The notification area is no longer imposing, distracting, and overwhelming.
    • With a pale background, but bordered and with icons.

Older notes are in updates_old.md.