sdkMigrations
constsdkMigrations:Readonly<{maxVersion:number;minVersion:number;sortedMigrations:Readonly<{steps:MigrationStep[];toVersion:number; }>[];validated:true; }>
Defined in: src/lib/db/schema.ts:220
Combined migrations for all SDK storage modules.
These migrations handle database schema upgrades from any previous version to the current version. The SDK manages all migration logic internally, so consumer apps don’t need to handle version arithmetic or migration merging.
Minimum supported version: v2 Migrations from v1 are not supported. Databases at v1 require a fresh install.
Migration history:
- v2 → v3: Added
was_stoppedcolumn to history table - v3 → v4: Added
modelPreferencestable for settings storage - v4 → v5: Added
errorcolumn to history table for error persistence - v5 → v6: Added
thought_processcolumn to history table for activity tracking - v6 → v7: Added
userPreferencestable for unified user settings storage - v7 → v8: BREAKING - Clear all data (embedding model change)
- v8 → v9: Added
thinkingcolumn to history table for reasoning/thinking content - v9 → v10: Added
projectstable andproject_idcolumn to conversations - v10 → v11: Added
mediatable for library feature, addedfile_idscolumn to history - v11 → v12: Added
chunkscolumn to history table for sub-message semantic search - v12 → v13: Added
parent_message_idcolumn to history table for message branching
Last updated on