feat(storage)!: drop SQLite support and legacy migration - #959
Merged
Merged
Conversation
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
1 participant
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.
Remove SQLite and the legacy database migration flow from startup, settings, IPC, and AI actions. Drop the dependencies and unused translations while preserving Markdown Vault compatibility.
Document upgrading through v5.12.0 before opening the vault in v6, including the v3 → v4.7.1 step and the macOS quarantine workaround.
BREAKING CHANGE: SQLite libraries must be converted to Markdown Vault using v5 before upgrading to v6.
Validation: scoped tests and lint, docs build, and frozen lockfile checks passed. The lifecycle test fails during initialization with an existing electron-store error; main typecheck reports an existing undeclared IPC channel in src/main/menu/main.ts. Both were checked against the original HEAD.