Ruby on Rails: Bug Fixes and Documentation Updates
Rails merged 11 pull requests on May 17-18, 2026, focusing on critical bug fixes for bulk job enqueueing, Active Record query methods, and phone number formatting, alongside major documentation improvements for caching and query interfaces.
Duration: PT2M12S
Transcript
Good morning, this is your Rails development briefing for May 18th, 2026.
The Rails team merged 11 pull requests over the past two days, addressing several important bug fixes and documentation updates.
Fatkodima merged a fix for bulk job and email enqueueing methods with no arguments, resolving issue #57264 by reorganizing code across ActionMailer and ActiveJob components. The same contributor also exposed additional BatchEnumerator attributes including cursor, order, and use_ranges, and merged a feature allowing developers to get the combined byte size of all attached blobs in Active Storage.
Tejanium fixed a range error in ActiveRecord's in_order_of method when passing out-of-range integers, preventing crashes when queries contain values exceeding database column limits.
Several database-related fixes were merged: tahsin352 resolved an issue with pre-serialized string values skipping cast operations in insert_all, while curi prevented false leaked-connection reports during connection pool reaper maintenance.
A phone number formatting bug was fixed by contributor 55728, correcting an issue where multi-character delimiters were incorrectly truncated in number_to_phone helpers.
Jean Boussier merged two significant changes: removing support for Rails 6.1 Active Record marshal format to allow future internal API evolution, and reverting schema cache sorting changes that were causing unexpected behavior in certain queries.
Documentation saw major improvements with Ridhwana completing substantial rewrites of both the Active Record Query Interface guide and the Caching with Rails guide, making them more readable and aligned with current Rails behavior.
What's next: The removal of Rails 6.1 marshal support may require attention from applications still using older cached data. The reverted schema cache changes suggest ongoing work to balance consistency with predictable query behavior.
That's your Rails update. We'll be back tomorrow with more development news.