Repository navigation
Conversation
CLI v5.11.3 supports database schema 22 while the desktop app writes schema 24, so WebDAV/S3 restore rejects the snapshot in validate_sql_user_version_for_import. Align the fresh-table DDL and migrations with upstream v23/v24, switch the Claude cursor update to an upsert so parser_state is not reset, and extend tests and fixtures through schema 24.
SaladDay
changed the title
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.
Upstream database snapshots with schema 23–26 currently fail to open or restore because the CLI only accepts schema 22. This PR follows upstream schema 26 at cf341a8, including its migrations and repairs for early WorkBuddy databases.
Existing upstream MCP/Skills flags and session parser state are preserved through migration, edits and sync. The sync protocol and remote layout stay unchanged; this adds database compatibility only, without new app management features. Schemas above 26 remain rejected. Once upgraded, the database cannot be opened by CLI v5.11.3 or earlier.
Fixes #553.
Validation:
cargo fmt --checkandcargo clippy --lib --no-default-featurespassed; Clippy reported 14 existing warnings outside the changed code.database::tests::init_rejects_unsafe_config_dir, fails on the system/tmpsymlink; the same failure was reproduced on the unchanged main baseline.