Skip to content

fix: re-run migrations after cloning new repo in cauldron_update #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Abourass merged 1 commit into from
Nov 19, 2025
Merged

fix: re-run migrations after cloning new repo in cauldron_update #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions update/cauldron_update.fish
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,16 @@ function cauldron_update -d 'Update Cauldron to the latest version'
# Now we remove the temp folder
rm -rf $tmp_dir

# Re-run schema and update migrations with the newly cloned files
# This ensures any new schema changes or migrations are applied to the restored database
if test -f $CAULDRON_PATH/data/schema.sql
sqlite3 $CAULDRON_DATABASE < $CAULDRON_PATH/data/schema.sql 2> /dev/null
end

if test -f $CAULDRON_PATH/data/update.sql
sqlite3 $CAULDRON_DATABASE < $CAULDRON_PATH/data/update.sql 2> /dev/null
end

# List of folders with functions
set CAULDRON_LOCAL_DIRS "alias" "cli" "config" "effects" "functions" "familiar" "internal" "setup" "text" "UI" "update"

Expand Down
Loading