Error Reporting Fix and Queue Classic Deprecation

Transcript

Good morning, this is Rails Daily for January 17th, 2026.

Two notable changes merged to Rails core yesterday.

Jean Boussier merged a fix for streaming template error reporting. Previously, when errors occurred during view streaming, they would only be logged and wouldn't reach error monitoring services like Sentry or Bugsnag that typically hook into Rails middleware. The change updates the streaming template renderer to use Rails.error, ensuring these errors are properly reported to integrated monitoring tools. This addresses a longstanding issue where streaming errors could go unnoticed in production monitoring dashboards.

Morgoth merged the deprecation of the queue_classic Active Job adapter. The queue_classic gem hasn't seen activity in two years, and an attempt to upstream the adapter directly to that project received no response. This marks the final Active Job adapter to be removed from Rails core as part of the ongoing effort to reduce maintenance burden. Applications using queue_classic will need to implement their own adapter or switch to an actively maintained job queue system.

Both changes include appropriate test coverage and changelog entries.

What's next: Developers using streaming views should see improved error visibility in their monitoring systems. Teams relying on queue_classic should plan migration to supported job backends before the next major Rails release.

That's your Rails Daily update. We'll be back tomorrow.