Repository navigation
fix: keep unlocked vaults in sync when moving their parent folder - #4383
Merged
Merged
Conversation
AlexAndBear
approved these changes
Nov 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Moving a folder that contains an unlocked vault (Move to, cut and paste, drag and drop) left the vault's key registered under the old path. A new vault created at that old path then opened without asking for a password and used the old vault's key.
After a successful move, the unlocked vaults inside the moved folder are now moved to the new path, the same way renames already handle it. If the move replaces an existing folder, the keys of vaults inside the replaced folder are dropped. Copies and moves between spaces are unaffected.
Related Issue