SYSTEM INFO:
Obsidian version: v1.4.13
Installer version: v1.4.5
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Insider build toggle: off
Live preview: off
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 1
Plugins enabled: 0
RECOMMENDATIONS:
none
Additional information
This problem is throwing off SUMo, a tool I use to track program updates and versions. It (correctly) reports 1.4.5 as being installed and out-of-date.
Isn’t this correct though? As your Debug info states your Installer version is 1.4.5
The Obsidian version is at 1.4.13 because you use the In-App auto update.
You can download the newest Installer and run it, your Installer version will be updated. You should do that anyways as 1.4.13 came with important security fixes for Electron.
So the solution should be something closer to what VScode does: it downloads the installer, executes it in the background, and then “switches over” at the user’s convenience.
What Obsidian appears to do, is indeed only update the files to go inside its Electron wrapper, so it isn’t a full update, but more like a patch towards a version that (largely) resembles the actual full update. This is bad, iyam, not only because of the aforementioned security updates that users will miss out on, but also performance and feature updates… and who knows what else.
The workaround is to only ever do manual updates by downloading & executing a new installer, but there is no solution as of yet, afaict.
This is how I understand it. Please correct me if you feel I got it wrong.
