// HACKER NEWS — CYBERSECURITY
Rails 8 Guide: Features, Requirements and Upgrade Path (2026)
Rails 8.0 shipped November 7, 2024 and requires Ruby 3.2.0+. Headline features:
a built-in authentication generator, Solid Queue/Cache/Cable (database-backed,
no Redis), Kamal 2 + Thruster deployment, Propshaft, and production-ready
SQLite. Rails 8.1 (October 2025) is the current release; Rails 8.0 now gets
security fixes only, through November 2026.
This guide walks through each Rails 8 feature with the commands and defaults
you’ll use. You’ll also find the current support timelines, a checklist for
upgrading from Rails 7.1 or 7.2, and a summary of what changed in Rails 8.1.
All version claims in this guide were verified against a fresh rails new app
on Rails 8.1.3.1 and Ruby 3.4.10.
Rails 8.0 and 8.1 both require Ruby 3.2.0 or newer. The rails gem enforces
this through its gemspec, so gem install rails fails on Ruby 3.1 or older. In
practice, you’ll want a newer Ruby than the minimum: the current Ruby 3.4 series
gets you YJIT improvements and the longest runway of Ruby security patches.
Here is where each recent Rails version stands, based on the Rails maintenance
policy as of August 2026:
Two takeaways from that table. First, Rails 8.0 is in its final stretch: it
receives security fixes only, and those stop on November 7, 2026. Second, both
7.1 and 7.2 are already off the supported list entirely. If you run either in
production, treat the upgrade checklist as
due now, not someday.
The minimum Ruby versions come from the Rails upgrade
guide, and the 8.1
feature set is documented in the Rails 8.1 release
notes.
Rails spent years shipping the building blocks of authentication:
has_secure_password in Rails 5, then normalizes, generates_token_for, and
authenticate_by in Rails 7.1.
Rails 8 assembles those pieces into a generator. One command scaffolds a
complete session-based authentication system, including database-backed sessions
and password resets:
The generator creates models, controllers, mailers, and views: