Release 2.1.1
Release notes for Obsibrain 2.1.1.
On this page
Fix updates in custom installation folders
Obsibrain now installs updates into the plugin folder recorded by Obsidian. This fixes update failures when the folder name differs from the plugin ID, including development copies in obsibrain-plugin.
Standard installations in plugins/obsibrain keep the same update path. Asset verification, backups, rollback, and user settings remain unchanged.
If an earlier version already fails to update
Standard installations can update normally. If an update already fails with ENOENT because of a custom plugin folder, the old updater cannot install this fix itself.
Close Obsidian, then replace main.js, manifest.json, and styles.css in the existing plugin folder with the files from this release. Keep data.json and all vault content. Reopen Obsidian afterward. Future updates use the recorded installation folder.
This release keeps the separate v1 and v2 update channels.