Rails Simplifies Parser Code and Fixes Console Reload
Rails removes legacy Ripper parser code after requiring Ruby 3.3, while also fixing console reload behavior and updating documentation. The changes streamline ActionView parsing and improve developer experience.
Duration: PT1M38S
Transcript
Good morning, this is Rails Daily for January 18th, 2026.
Three pull requests merged yesterday as Rails continues its modernization efforts. Earlopain merged a significant cleanup that removes dead compatibility code with Ripper. With Rails now requiring Ruby 3.3, which includes Prism as a default gem, the framework no longer needs to maintain dual parser support. This change eliminates over 500 lines of legacy code across ActionView's render parser and Railties' annotation extractor, consolidating everything to use Prism exclusively.
Ben Sheldon addressed a console issue where reload! wasn't properly resetting the console's executor when present. This fix resolves problems with stale state persisting after console reloads, improving the development experience for Rails applications using the executor pattern.
MDH contributed a documentation update to ActiveRecord's finder methods, modernizing examples that still used outdated array notation instead of the current hash syntax. While a small change, it helps prevent confusion for developers new to Rails.
All three changes were merged by Jean Boussier, indicating active maintenance of the Rails codebase as the framework prepares for its next release cycle.
What's next: Watch for additional Ruby 3.3 compatibility improvements as Rails continues dropping legacy code. Console and development experience enhancements remain a focus area.
That's your Rails Daily update. We'll be back Monday with the latest from the Rails repository.