$ the-wire · showcase
RAILS KILLS SCHEMA_MIGRATIONS MERGE CONFLICTS
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
Rails just shipped a way to dump your migration versions directly into schema.rb, eliminating the version kwarg conflicts that plague multi-branch development.
The new flag lets you include schema_migrations in db/schema.rb [1], solving two long-standing pain points: the assumption problem when loading schema and the merge conflicts that spike when two branches land new migrations simultaneously. When enabled, db:schema:dump now appends migration versions to the end of your schema file, letting Rails load them without guessing what's been applied. In parallel, Rails addressed a MySQL transaction isolation bug [2] where multi-statement retries were actually increasing database round trips instead of reducing them. The fix brings separate statements back while preserving the isolation level across retries. Tailwind CSS bumped to 4.3.2 [3] tracking upstream, and Ruby 3.3.12 landed in the devcontainer [4] for teams using the official Rails dev environment.
Action items
- → Review the schema_migrations dump feature and enable if you're tired of merge conflicts in schema.rb rails/rails [plan]
- → Update tailwindcss-rails to 4.3.2 if you're on the CSS desk rails/tailwindcss-rails [monitor]
- → Pull Ruby 3.3.12 into your devcontainer if you maintain infrastructure rails/devcontainer [monitor]
References
- [1] Support dumping schema_migrations in db/schema.rb ↗ rails/rails
- [2] Don't force multi statement for MySQL tx isolation ↗ rails/rails
- [3] build(deps): bump tailwindcss-ruby from 4.3.1 to 4.3.2 ↗ rails/tailwindcss-rails
- [4] Add Ruby version: 3.3.12 ↗ rails/devcontainer
