The Wire · Showcase
RAILS TEST SUITE GETS CLEANER, POSTGRES TIMEZONE FIX LANDS
By RepoJournal · Filed · About Rails
Rails core just shipped a wave of test infrastructure improvements and a critical Postgres timezone handling fix that eliminates edge cases in parameter status checks.
The test cleanup effort continues with `NotificationAssertions` helpers now applied across `activerecord` tests, removing manual `ActiveSupport::Notifications.subscribe` patterns that made test code harder to follow [1]. This follow-up to earlier notification assertion work consolidates testing patterns in `asynchronous_queries_test.rb`, `connection_pool_test.rb`, and `relation/load_async_test.rb`. Meanwhile, the Postgres adapter got smarter about timezone handling: the fix ensures timezones are only set when actually needed, with case-insensitive treatment of `variables` keys to work cleanly with parameter status checks [2]. On the documentation side, the Active Storage guide received a significant overhaul that restructures content for better coherence, clarifies the distinction between proxy and redirect modes, and corrects confusing text about how `.attach` works with `has_many_attached` associations [3]. These are the kinds of foundational improvements that pay dividends across every Rails app.
Action items
- → Review test patterns in your activerecord test suite and adopt NotificationAssertions where applicable rails/rails [plan]
- → Check Active Storage guide for the clarifications on proxy vs. redirect modes and processed option rails/rails [monitor]
- → If using Postgres with timezone-aware columns, verify behavior after the parameter status fix merges to main rails/rails [monitor]
References
- [1] Simplify more ```activerecord``` tests with ```NotificationAssertions``` helpers ↗ rails/rails
- [2] Only set Postgres timezone when needed ↗ rails/rails
- [3] [RF-Docs] [ci-skip] Active Storage Guide ↗ rails/rails
FAQ
- What changed in Rails on May 28, 2026?
- Rails core just shipped a wave of test infrastructure improvements and a critical Postgres timezone handling fix that eliminates edge cases in parameter status checks.
- What should Rails teams do about it?
- Review test patterns in your activerecord test suite and adopt NotificationAssertions where applicable • Check Active Storage guide for the clarifications on proxy vs. redirect modes and processed option • If using Postgres with timezone-aware columns, verify behavior after the parameter status fix merges to main
- Which Rails repositories shipped on May 28, 2026?
- rails/rails