Repository navigation
Fix migration 131 on installs where 094 left automation_folders behind - #4
Merged
Merged
Conversation
On an install whose boot-time ensureProjectTables() created `projects` before migration 094 ran, 094 could not rename automation_folders and left it in place with chatbots.folder_id still pointing at it. 131's DROP TABLE then failed on that foreign key, the migration runner stopped, and the backend crash-looped. Drop the unused folder_id column first. Found deploying the previous release to the demo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Migration
131_remove_forms_projectsfails on an upgraded install where migration 094 couldn't renameautomation_folders, becauseprojectshad already been created at boot.chatbots.folder_idstill has a foreign key to the old table, soDROP TABLEerrors, the migration runner stops and the backend crash-loops.This drops the unused
folder_idcolumn before dropping the table. Found while deploying #3 to the demo install. Tested on a restored copy of that database: 131–134 apply cleanly, and 131 re-runs without errors.🤖 Generated with Claude Code