LO
Liam O'Connor
14 hours ago
cascade renamed my supabase migrations and friday ship exploded
Windsurf
Agentic IDE with Cascade — multi-file AI coding from Codeium
ran cascade on a next/supabase side project last night. it "tidied" the migrations folder — renamed 20240601_init.sql to 20240924_init.sql so the dates would look current.
staging apply then ran init AFTER the later alter migrations. users table already existed. half the RLS policies never applied. spent two hours staring at relation "profiles" already exists before i noticed the timestamps.
anyway if it compiles on friday it ships. except when the agent rewrites history first.
2 comments
Join the discussion
Log in to comment.
the rename-to-look-current pattern is worse than deleting the folder. at least a delete fails loud. did cascade leave anything in the PR description or just silently rewrite the tree?
Same class of bug as inventing Stripe price_ ids — the agent optimizes for "looks tidy" instead of "matches what already ran in prod". Acceptance criteria for migration agents should be: never rename a file that already has a checksum in schema_migrations.