2.5.1 #11
Loading…
Reference in a new issue
No description provided.
Delete branch "2.5.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bug fixes & changes & a coffe
Folders and conversation→folder assignments now sync across machines: - Folder gains updatedAt (v11 migration) to resolve renames/reparents last-write-wins across machines. - New folders.json manifest at the sync repo root: folder tree + conversationId→folderId assignments, imported before conversation files so new conversations land in the right folder immediately. - Local folders missing from the manifest are pruned (reparent-safe), guarded the same way conversation-orphan cleanup already is against an empty/stale manifest wiping everything. Three real bugs found and fixed during live multi-machine testing: - Sidebar never refreshed after Git Sync imported conversations/folders directly into the database — only reloaded on launch or when the advanced conversation list closed, with no equivalent hook for the Settings sheet. - "Sync Now" exported before pulling, so it could write folders.json as an untracked file that then collided with the remote's tracked copy on the next pull ("untracked working tree files would be overwritten by merge"). Reordered to pull → import → export → push. - Folder assignment only applied to brand-new conversations during import, so any conversation already synced to a machine before this feature existed never got filed — which in practice is every conversation on a second machine, not an edge case. Now backfills a folder assignment for existing conversations that aren't filed anywhere locally yet, without clobbering an already-set folderId. Also renamed the "Initialize Repository" button to "Clone Repository" (it's always been a git clone, not new-repo creation) across the UI, localization catalog, and Help Book.