Ruby on Rails 8.0

Rails 8.0 raises the minimum Ruby version to Ruby 3.2. New applications use the database-backed Solid Queue, Solid Cache, and Solid Cable components by default, reducing the need for Redis for background jobs, caching, and Action Cable. Existing applications are not automatically moved to those adapters. Rails 8.0 also adds an authentication generator for a conventional password-based authentication starting point, and Action Controller adds Parameters#expect for requiring and permitting an expected parameter shape in one operation.

Rails 8.0 remains within its supported window, so staying on the latest 8.0 patch level does not create an immediate upstream-maintenance gap. The practical trade-off is that newer Rails lines can add framework capabilities, fixes, and compatibility work that 8.0 will not receive. Over time, application dependencies, Ruby versions, browser tooling, and deployment conventions may increasingly target newer Rails versions. Deferring the move can also accumulate deprecations and configuration differences, making the eventual upgrade broader and harder to validate.

Keep the application on the latest available Rails 8.0 patch release and run its full test suite and production-like smoke checks after each update. Confirm that the deployed Ruby version meets Rails 8.0's minimum requirement, and inventory gems, JavaScript tooling, database adapters, and operational services for their Rails and Ruby compatibility. For a move to a newer Rails line, create an upgrade branch, review the target release notes and upgrade guide, run bin/rails app:update only as a source of configuration diffs, and apply changes deliberately. Treat framework deprecation warnings as upgrade work, add coverage around authentication, jobs, caching, WebSocket behavior, and asset delivery, and verify any use of Redis or the Solid adapters before changing infrastructure.