Ruby on Rails: Two Major Reverts
The Rails team reverted two significant features on May 15th - the ActiveModel::Conversion render_in implementation and automatic schema column sorting. Both reverts address integration issues discovered after initial implementation.
Duration: PT2M
https://podlog.io/listen/ruby-on-rails-87e2c2b6/episode/ruby-on-rails-two-major-reverts-1f151259
Transcript
Good morning. This is your Ruby on Rails briefing for May 16th, 2026.
Yesterday saw two notable reverts in the Rails codebase. Sean Doyle merged a revert of the default render_in implementation for ActiveModel::Conversion. This feature, which was intended to streamline view rendering for ActiveModel objects, was pulled back due to a critical issue with controller-based view partial namespacing. The implementation wasn't properly incorporating render context, which could lead to incorrect partial resolution in namespaced controllers.
Bert McCutchen also merged a revert of the automatic table column sorting feature in schema dumps. Originally introduced to provide consistent schema output, the sorting approach was determined to be an inappropriate solution to the underlying problem developers were experiencing. The revert removes the alphabetical column ordering from ActiveRecord's schema dumper, returning to the original column order preservation.
Both reverts demonstrate the Rails team's commitment to stability over convenience. The ActiveModel::Conversion feature removed 128 lines across seven files, including changes to ActionView tests, ActiveModel core files, and documentation. The schema dumper revert was more targeted, affecting only the dumper logic and associated tests.
These weren't simple rollbacks - both authors indicated plans for redesigned implementations. The render_in functionality is expected to return with proper namespace handling, while the schema column issue will likely see a different approach that addresses the root cause rather than sorting symptoms.
What's next: Watch for revised pull requests that address the underlying issues while maintaining Rails' integration standards. The team is also updating documentation to reflect these changes and prevent similar integration oversights.
That's your Rails update. We'll continue monitoring the codebase for the reimplemented features.