Background
We've successfully migrated from SQLite-based persistence to file-based persistence.
The SQLite dependency (@sqlite.org/sqlite-wasm) is currently kept for backward compatibility to support automatic migration of existing databases.
Tasks
After a reasonable migration period (e.g., 2-3 releases), we should:
Migration Period
Suggested timeline:
- Now: v4.2.0 - File-based persistence with auto-migration
- After 2-3 releases: v4.5.0 or v5.0.0 - Remove SQLite completely
Notes
Users who haven't migrated by then can:
- Downgrade temporarily to migrate
- Manually recreate their conversation state (it's just metadata, not critical data)
- The plan files are preserved regardless (most important data)
Background
We've successfully migrated from SQLite-based persistence to file-based persistence.
The SQLite dependency (
@sqlite.org/sqlite-wasm) is currently kept for backward compatibility to support automatic migration of existing databases.Tasks
After a reasonable migration period (e.g., 2-3 releases), we should:
@sqlite.org/sqlite-wasmfrompackages/core/package.jsonpackages/core/src/database.tspackages/core/src/migration.ts(migration utilities)FileStorageconstructor to not need legacy SQLite path formatMigration Period
Suggested timeline:
Notes
Users who haven't migrated by then can: