Ruby on Rails End of Life —
Every Version EOL Date & Upgrade Guide
Ruby on Rails is one of the most influential web frameworks ever built — and like all long-lived frameworks, it has accumulated a significant trail of unsupported versions running in production. Rails 5, Rails 6, and even Rails 4 applications are still serving real traffic. The Rails core team maintains a lean security policy: only the most recent minor version of the most recent two major versions receives security patches. Everything else is on its own.
This guide covers the official Rails end-of-life schedule, EOL Risk Scores for each version, and what the maintenance policy means for your application's CVE exposure.
Key Dates at a Glance
- Rails 8.1: bug fixes end 2026-10-10; security fixes end 2027-10-10
- Rails 8.0: bug fixes end 2026-05-07; security fixes end 2026-11-07
- Rails 7.2: bug fixes end 2025-08-09; security fixes end 2026-08-09
- Rails 7.1: bug fixes end 2024-10-01; security fixes end 2025-10-01
- Rails 7.0: bug fixes end 2023-10-15; security fixes end 2025-04-01
- Rails 6.1: bug fixes end 2021-12-15; security fixes end 2024-10-01
Complete Rails EOL Schedule
The Rails project publishes an official maintenance policy that defines which versions are in full maintenance (bug fixes + security fixes), security maintenance only (security fixes only, no bug fixes), and unsupported (no fixes of any kind).
| Version | Release | End of Life | Status | EOL Risk Score™ |
|---|---|---|---|---|
| Rails 4.2 | Dec 2014 | Apr 2017 | EOL | 80 |
| Rails 5.2 | Apr 2018 | Jun 2022 | EOL | 80 |
| Rails 6.0 | Aug 2019 | Jun 2023 | EOL | 80 |
| Rails 6.1 | Dec 2020 | Oct 1, 2024 | EOL | 75 |
| Rails 7.0 | Dec 2021 | Apr 1, 2025 | EOL | 75 |
| Rails 7.1 | Oct 2023 | Oct 1, 2025 | EOL | 70 |
| Rails 7.2 | Aug 2024 | Aug 9, 2026 | EOL | 65 |
| Rails 8.0 | Nov 2024 | Nov 7, 2026 | Warning | 55 |
| Rails 8.1 | Oct 2025 | Oct 10, 2027 | Supported | 40 |
Rails 6 — End of Life (6.1 Ended October 1, 2024)
Rails 6 introduced Action Mailbox, Action Text, parallel testing, and multiple database support. It was a major feature release that many teams adopted and have stayed on. Rails 6.0 reached EOL in June 2023; Rails 6.1 followed in October 2024. Both are now unsupported.
Rails 6.x applications typically run on Ruby 2.6, 2.7, or 3.0 — all of which have their own EOL status. Ruby 2.6 reached end of life in March 2022; Ruby 2.7 in March 2023; Ruby 3.0 in March 2024. A Rails 6 application running on Ruby 2.7 has two compounding EOL layers.
Rails 7 — Entire Line End of Life (7.2 Ended August 9, 2026)
Rails 7 introduced Hotwire (Turbo + Stimulus) as the default JavaScript approach, replacing Webpacker. Rails 7.0 reached EOL on April 1, 2025, Rails 7.1 followed on October 1, 2025, and Rails 7.2's security support ended on August 9, 2026 — the entire Rails 7 line is now end-of-life. Rails 8.0 is next: its EOL lands November 7, 2026, so the safe target today is Rails 8.1 (supported until October 2027).
If you are on any Rails 7.x release, no stop short of Rails 8 keeps you supported — 7.1 and 7.2 are both past EOL. Step through 7.1 and 7.2 for the deprecation warnings, but the destination is 8.1.
Rails 8 — Latest Release
Rails 8.0 was released in November 2024 and represents a significant step in Rails' evolution toward simplicity and self-contained deployment. It ships with Solid Cache, Solid Queue, and Solid Cable — database-backed implementations of caching, background jobs, and WebSockets that reduce external infrastructure dependencies. It also includes Kamal 2 for container-based deployment and Thruster for HTTP asset caching.
Rails 8 requires Ruby 3.2 or later. If you are on Ruby 3.1 or earlier, you will need to upgrade Ruby first before targeting Rails 8.
Understanding the Rails Maintenance Policy
The Rails maintenance policy is simple but easy to misread. At any given time, only the latest patch release of the two most recent minor versions within a supported major receives security fixes. When a new minor version is released, the previous one enters a transition period and then goes unsupported.
Ruby on Rails currently carries an EOL Risk Score™ of 65/100 — Grade D, high risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the Ruby on Rails lifecycle page.
The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.
Upgrading Rails Safely
Upgrade one minor version at a time
The Rails team's official guidance is to upgrade incrementally: 6.0 → 6.1 → 7.0 → 7.1 → 7.2 → 8.0 → 8.1. Each minor version includes deprecation warnings for APIs removed in the next version. Skipping versions means missing those warnings and hitting breaking changes blind.
Use the upgrade guide
The Rails Guides include a dedicated upgrade guide for each version pair. Always start there — it documents every breaking change, configuration requirement, and default behavior change introduced in the new version.
Run with both old and new defaults
Rails uses the config/application.rb load_defaults value to control which new defaults are active. After upgrading the gem, set load_defaults to the new version number and address failures one at a time before switching fully.
Check your Ruby version first
Each Rails version has a minimum Ruby requirement. Check the Ruby EOL page and ensure your Ruby version is both compatible with your target Rails version and not itself EOL. Rails 8 requires Ruby 3.2+.
Frequently Asked Questions
Is Rails 7 still supported?
No. The whole Rails 7 line is end of life: Rails 7.2’s security fixes ended 2026-08-09, Rails 7.1’s on 2025-10-01 and Rails 7.0’s on 2025-04-01. An application on any 7.x release is receiving no security patches. The supported releases today are Rails 8.1 and, for security fixes only, Rails 8.0.
Which Rails versions are currently supported?
Rails 8.1 receives bug fixes until 2026-10-10 and security fixes until 2027-10-10. Rails 8.0 is in its security-only phase: bug fixes ended 2026-05-07 and security fixes end 2026-11-07. Everything older — 7.2, 7.1, 7.0, 6.x and earlier — is unsupported.
What is the Rails maintenance policy?
Since Rails 7.1 the core team publishes dated windows for every minor release: roughly one year of bug fixes and two years of security fixes from release. Rails 8.0, released 2024-11-07, shows the pattern — bug fixes ended 2026-05-07 and security fixes end 2026-11-07. Once a release leaves its security window nothing is backported to it, whatever the severity.
When does Rails 8.0 reach end of life?
Rails 8.0 security support ends 2026-11-07. It is already past its bug-fix window, so the only changes still landing on 8.0 are security patches. Teams on 8.0 should plan the move to 8.1 before November rather than treating 8.0 as a long-term home.
Is Rails 6.1 end of life?
Yes. Rails 6.1 reached end of life on 2024-10-01 and Rails 6.0 on 2023-06-01. Both have been without security fixes for years, and the Ruby versions they usually run on (2.6 through 3.0) are end of life too — two unpatched layers in one application.
Is there long-term or extended support for old Rails versions?
Not from the Rails project, which ships no LTS line. Independent vendors do sell extended security support for out-of-support Rails releases — backported fixes for a paid subscription — and that is the realistic bridge for an application that cannot upgrade this quarter. Tell us your version via the form on this page and we will reply with matched options and an honest view of whether an upgrade is the cheaper path.
How do I check which Rails version I am running?
Run bundle exec rails --version from the application directory, or look for the rails (x.y.z) line in Gemfile.lock. The Gemfile.lock is the authoritative answer for a deployed app, because it pins the exact version that is actually loaded.
Do I need to upgrade Ruby to move to Rails 8?
Usually. Rails 8 requires Ruby 3.2 or later, so an application on Ruby 3.1 or older has to upgrade Ruby first — and the Ruby upgrade is often the larger job because of gem compatibility. Plan the two together and upgrade one Rails minor at a time (7.0 → 7.1 → 7.2 → 8.0 → 8.1) so each release’s deprecation warnings surface before the next step.
What does “security fixes only” actually mean?
The release still receives patches for reported vulnerabilities but no bug fixes, performance work or compatibility updates. It is safe to run for the remaining window and nothing more: when the security date passes, the next CVE disclosed against that release stays open permanently.