v0.2.87
What's fixed
Logseq sync: no more duplicate version nodes
Repeatedly editing the same Logseq note used to leave many stale old-version nodes "active" in your brain, cluttering the browse list. This release makes old versions correctly retire (heat decays to the floor) so only the current version stays prominent.
Root causes addressed:
- Old versions that fell out of the current note state are now reliably retired (set-difference reconciliation instead of brittle positional matching).
- Emptying or trimming a note now retires its old nodes instead of orphaning them — while files that are merely offline (iCloud "optimize storage") are left untouched.
- Concurrent saves of the same file are serialized, so a slow digest can't lose the newer save.
- Pure-separator / empty-bullet blocks no longer create zero-information nodes.
- Date-named pages outside
journals/are now treated consistently as journals (correct created date + age-based heat). - Shutdown now waits for in-flight note processing to finish before closing the database, preventing orphaned nodes when you quit.
No action needed — old duplicate versions decay on their own after upgrading.