You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Schema history now lives in a leaf_schema_history table inside the database being migrated, so each environment knows what was actually applied to it instead of trusting local files
Your first db:migrate imports existing storage/database snapshots into the new table automatically, and tables with no history are adopted from their current schema file instead of being recreated
Seeds accept full faker expressions: '@faker.unique.safeEmail', '@faker.numberBetween(1, 5)', anything faker can do. The old primitive tokens still work
Test suite and CI now run through Alchemy
Fixed
Fixed schema file name loading
Changed
Rollbacks no longer rewrite your schema files. A rollback changes only the database and its history, leaving your .yml files exactly as you wrote them — after rolling back, run db:migrate to re-apply the file or edit it to match
Each environment builds its own history the first time it migrates, so deploys need to run migrations per environment
Schema now requires PHP 8.2+ and jumps from v0.1.1 to v5.0 to version alongside the rest of Leaf 5