The Wire · Showcase
JBUILDER CUTS MEMORY WITH OPTIMIZATION SUITE
By RepoJournal · Filed · About Rails
Jbuilder 2.15.0 shipped performance wins across the entire rendering pipeline while Rails core quietly reverted two incomplete features headed for 8.2.
The Jbuilder team landed a focused optimization sprint that reduces memory allocations in `array!` and `set!` calls by eliminating unnecessary splat operations, while also optimizing the `KeyFormatter` cache path [1][2]. Over on rails/rails, the team reverted an incomplete `ActiveModel::Conversion#render_in` implementation after discovering it didn't properly handle controller-based view namespacing, which was never released so the revert is clean [3][4]. A second revert addressed schema column sorting in dumps, which the core team determined wasn't the right approach to the underlying problem [5]. Meanwhile, Jbuilder also aligned scaffold generation with Rack 3.1's HTTP 422 status code change from `:unprocessable_entity` to `:unprocessable_content` [6]. Thor fixed false positive warnings from mock frameworks that were polluting test output by distinguishing between user-defined and gem-defined methods [7].
Action items
- → Update to Jbuilder 2.15.0 for performance gains in collection rendering rails/jbuilder [plan]
- → Review any custom render_in implementations before Rails 8.2 final rails/rails [monitor]
- → Update Thor to suppress test framework warnings rails/thor [plan]
References
- [1] v2.15.0 ↗ rails/jbuilder
- [2] Optimize `array!` and `set!` ↗ rails/jbuilder
- [3] Revert "Add default `#render_in` implementation to `ActiveModel::Conversion`" ↗ rails/rails
- [4] Merge pull request #57374 from seanpdoyle/revert-pr-57349 rails/rails
- [5] Revert: Sort table columns by name when dumping schema ↗ rails/rails
- [6] Use `:unprocessable_content` for scaffolds with Rack 3.1 or higher ↗ rails/jbuilder
- [7] Suppress false positive warnings from gem-defined methods ↗ rails/thor
FAQ
- What changed in Rails on May 16, 2026?
- Jbuilder 2.15.0 shipped performance wins across the entire rendering pipeline while Rails core quietly reverted two incomplete features headed for 8.2.
- What should Rails teams do about it?
- Update to Jbuilder 2.15.0 for performance gains in collection rendering • Review any custom render_in implementations before Rails 8.2 final • Update Thor to suppress test framework warnings
- Which Rails repositories shipped on May 16, 2026?
- rails/jbuilder, rails/rails, rails/thor