Skip to content

1.6.2

Latest

Choose a tag to compare

@github-actions github-actions released this 08 Aug 16:27
34d4bb7

Tells you to restart after an update, instead of silently copying nothing

Updating a plugin while Obsidian is running leaves the previous build partly alive. Menus and commands still register and the copy still reports success, but nothing reaches the clipboard. You paste and get whatever you copied last, which looks like a broken release rather than a stale process. Restarting Obsidian clears it.

Pubcopy now notices when its files changed underneath a running Obsidian and says so:

Pubcopy updated from 1.6.1 to 1.6.2. Restart Obsidian, or disable and re-enable the plugin, before copying. Until then copying may do nothing.

It appears once per update, not on every load.

What it deliberately does not do

No warning on a cold start. If you update with Obsidian closed, the new build is read fresh from disk and nothing is stale, so no notice appears. Telling you to restart the app you just opened would be wrong.

It cannot break the plugin. The check runs after everything else is registered and ignores its own failure to save. On a read-only vault, a full disk, or with a sync client holding the settings file open, you keep your commands, menus, and settings tab.

Nothing about conversion changed.