When running web applications, you’ll eventually face the question: “How long is our Rails version supported?” Missing the point when security patches stop can lead to serious problems. This guide provides accurate information about Ruby on Rails End of Life (EOL) schedules.
1. What is Ruby on Rails?
Ruby on Rails (Rails or RoR) is a server-side web application framework written in Ruby. First released by David Heinemeier Hansson in 2004 while working on the Basecamp project, it has served as the backbone for countless web services for over 20 years.
Major services like GitHub, Shopify, Airbnb, and Twitch are built with Rails. Developers worldwide continue using Rails to efficiently build web applications. By emphasizing “Convention over Configuration” and “DRY (Don’t Repeat Yourself)” principles, Rails helps developers focus more on business logic.
Rails is based on the MVC (Model-View-Controller) pattern and consists of various components including Active Record (ORM), Action Pack (routing and controllers), Action View (view templates), Active Job (background jobs), and Action Cable (WebSocket).
2. New Support Policy Starting with Rails 7.2
On October 15, 2024, the Rails team made an important announcement: a completely new Maintenance Policy would apply starting with Rails 7.2.
Key Points of the New Policy:
- Bug Fixes: 1 year from minor version release date
- Security Fixes: 2 years from minor version release date
- Full End of Life (EOL) after that
For example, if Rails 8.0.0 was released on November 7, 2024:
- Bug fixes: Until November 7, 2025
- Security patches: Until November 7, 2026
- EOL: November 7, 2026
This policy applies only to Rails 7.2 and later versions. Earlier versions follow the previous flexible support policy.
Official policy documentation: Ruby on Rails Maintenance Policy
3. Detailed Schedule by Rails Version
As of October 2025, here are the exact support schedules for each Rails version.
Currently Supported Versions (Active Support)
| Version | Release Date | Bug Fixes End | Security Support End (EOL) | Latest Patch | Status |
|---|---|---|---|---|---|
| 8.0.x | 2024-11-07 | 2025-11-07 | 2026-11-07 | 8.0.3 | 🟢 Full Support |
| 7.2.x | 2024-08-09 | 2025-08-09 | 2026-08-09 | 7.2.2.2 | 🟢 Full Support |
| 7.1.x | 2023-10-05 | 2024-10-05 (Ended) | 2025-10-01 | 7.1.5.2 | 🟡 Security Only |
| 7.0.x | 2021-12-15 | 2024-10-15 (Ended) | 2025-04-01 | 7.0.8.7 | 🟡 Security Only |
End of Life Versions (EOL)
| Version | Release Date | Bug Fixes End | EOL Date | Final Version | Status |
|---|---|---|---|---|---|
| 6.1.x | 2020-12-09 | 2023-10-01 | 2024-10-01 | 6.1.7.10 | 🔴 EOL |
| 6.0.x | 2019-08-16 | 2022-06-01 | 2023-06-01 | 6.0.6.1 | 🔴 EOL |
| 5.2.x | 2018-04-09 | 2021-06-01 | 2022-06-01 | 5.2.8.1 | 🔴 EOL |
| 5.1.x | 2017-04-27 | 2018-08-25 | 2019-08-25 | 5.1.7 | 🔴 EOL |
| 5.0.x | 2016-06-30 | 2017-04-01 | 2018-04-01 | 5.0.7.2 | 🔴 EOL |
| 4.2.x | 2014-12-19 | 2016-06-30 | 2017-04-27 | 4.2.11.3 | 🔴 EOL |
| 4.1.x | 2014-04-08 | 2015-06-25 | 2016-04-08 | 4.1.16 | 🔴 EOL |
| 4.0.x | 2013-06-25 | 2014-12-19 | 2015-06-25 | 4.0.13 | 🔴 EOL |
| 3.2.x | 2012-01-20 | 2014-06-25 | 2016-06-30 | 3.2.22.5 | 🔴 EOL |
| 3.1.x | 2011-08-31 | 2012-06-01 | 2013-06-25 | 3.1.12 | 🔴 EOL |
| 3.0.x | 2010-08-29 | 2011-06-01 | 2012-06-25 | 3.0.20 | 🔴 EOL |
| 2.3.x | 2009-03-15 | 2011-06-01 | 2013-06-25 | 2.3.18 | 🔴 EOL |
Note: Starting with Rails 4.2, EOL dates were officially announced. For earlier versions, EOL dates are estimated based on the release of the next major version.
Sources: endoflife.date/rails, RubyGems Rails Versions, Rails GitHub
4. Detailed Status by Version
Rails 8.0 – Latest Major Release
Released on November 7, 2024, Rails 8.0 is currently the latest version. Unveiled at Rails World 2024, it features deployment simplification through Kamal 2 and integration of the “Solid” series including Solid Queue and Solid Cache.
- Bug fixes: Until November 7, 2025
- Security support: Until November 7, 2026
- Latest version: 8.0.3 (as of March 2025)
For new projects, Rails 8.0 is the recommended choice.
Rails 7.2 – Stable Latest Version
Released on August 9, 2024, Rails 7.2 is the first version with the new maintenance policy applied.
- Bug fixes: Until August 9, 2025
- Security support: Until August 9, 2026
- Latest version: 7.2.2.2 (as of August 2025)
If upgrading directly to Rails 8.0 seems daunting, 7.2 is a very stable choice.
Rails 7.1 – Security Support Only
Released on October 5, 2023, Rails 7.1 has ended bug fix support and only provides security patches.
- Bug fixes: Ended October 2024
- Security support: Until October 1, 2025
- Latest version: 7.1.5.2
After October 2025, security patches will also stop, so plan to upgrade to 7.2 or later by September 2025 at the latest.
Rails 7.0 – EOL Approaching
Released on December 15, 2021, Rails 7.0 was originally scheduled for EOL in 2023, but support was extended during the new policy transition period.
- Bug fixes: Ended October 2024
- Security support: Until April 1, 2025 (Extended)
- Latest version: 7.0.8.7
Important: After April 2025, no security patches will be provided. If you’re using Rails 7.0, you need to plan your upgrade immediately.
Official announcement: New Rails maintenance policy and end of maintenance announcements
Rails 6.1 – Already EOL
Released in December 2020, Rails 6.1 officially reached EOL on October 1, 2024. The Rails team provided one additional security patch (6.1.7.9, 6.1.7.10) during the policy transition, but support is now completely ended.
- Released: December 9, 2020
- EOL: October 1, 2024
- Final version: 6.1.7.10
- Key features: Per-database connection switching, horizontal database sharding, Delegated Types
If you’re still using Rails 6.1, you need to upgrade immediately.
Rails 6.0 and Earlier Versions – Legacy Versions
| Version | Key Features | EOL | Note |
|---|---|---|---|
| 6.0 | Webpack default, Action Mailbox, parallel testing | June 2023 | EOL 4 years ago |
| 5.2 | ActiveStorage, Redis cache store | June 2022 | EOL 5 years ago |
| 5.1 | Yarn, Webpack support, system tests | August 2019 | EOL 8 years ago |
| 5.0 | Action Cable, API mode, Turbolinks 5 | April 2018 | EOL 9 years ago |
| 4.2 | Active Job, async emails | April 2017 | EOL 10 years ago |
| 4.1 | Spring, Variants, Enums | April 2016 | EOL 11 years ago |
| 4.0 | Strong Parameters, Turbolinks | June 2015 | EOL 12 years ago |
| 3.2 | Fast development mode, Asset Pipeline improvements | June 2016 | EOL 11 years ago |
| 3.1 | Asset Pipeline, CoffeeScript, Sass | June 2013 | EOL 14 years ago |
| 3.0 | Merb integration, Bundler introduction | June 2012 | EOL 15 years ago |
| 2.3 | Templates, engines, Rack integration | June 2013 | EOL 14 years ago |
Warning: All these versions reached EOL years ago and are exposed to serious security risks. If you’re using any of these, you must upgrade to the latest version immediately.
5. What Happens After EOL?
When a Rails version reaches EOL, the following issues occur:
Security Vulnerabilities Exposed This is the most serious problem. No official patches are provided even when new security vulnerabilities are discovered. You become defenseless against critical vulnerabilities like SQL injection, Remote Code Execution (RCE), and Cross-Site Scripting (XSS).
Compliance Issues For services that must comply with regulations like HIPAA, PCI DSS, SOC2, or GDPR, using end-of-life software can result in audit failures or fines.
Compatibility Issues Compatibility problems may arise with the latest Ruby versions, databases, web servers, and browsers. Many new gem libraries also stop supporting older Rails versions.
Recruitment and Maintenance Difficulties Developers who want to learn current technologies avoid legacy versions, making it harder to recruit and retain good developers.
6. Upgrade Roadmap Strategy
Here are recommended strategies based on your current version:
Version-Specific Upgrade Strategy Summary
| Current Version | Urgency | Recommended Upgrade Path | Target Completion |
|---|---|---|---|
| Rails 2.x-3.x | 🔴 Critical | 2.x → 3.2 → 4.2 → 5.2 → 6.1 → 7.0 → 7.2 | Start immediately (months required) |
| Rails 4.x | 🔴 Critical | 4.x → 5.2 → 6.1 → 7.0 → 7.2 | Start immediately (2-3 months) |
| Rails 5.x | 🔴 Urgent | 5.x → 6.1 → 7.0 → 7.2 | Start immediately (1-2 months) |
| Rails 6.0-6.1 | 🔴 Urgent | 6.x → 7.0 → 7.2 | By January 2025 |
| Rails 7.0 | 🟠 High | 7.0 → 7.1 → 7.2 or 8.0 | By March 2025 |
| Rails 7.1 | 🟡 Medium | 7.1 → 7.2 or 8.0 | By September 2025 |
| Rails 7.2 | 🟢 Safe | Regular patch updates only | – |
| Rails 8.0 | 🟢 Latest | Regular patch updates only | – |
Detailed Upgrade Strategies
If Using Rails 5.x or Earlier This is extremely urgent. These versions have been EOL for years and have unpatched known security vulnerabilities.
Gradual Approach (Recommended):
- Build Test Environment First: Ensure adequate test coverage (minimum 60%+)
- Upgrade Step by Step: Rails 4.x → 5.2 → 6.1 → 7.0 → 7.2
- Stabilize Each Step: Allow at least 1-2 weeks testing period
- Update Dependent Gems: Replace with compatible gems for each Rails version
Or Consider Full Rewrite:
- If Rails version is too old (Rails 3.x or earlier)
- If code quality is poor and tests are lacking
- If business logic has changed significantly
If Using Rails 6.1 or Earlier Immediate upgrade needed. A gradual approach is safest:
- Rails 6.1 → Rails 7.0 (Requires Ruby 2.7+)
- Rails 7.0 → Rails 7.1 (Requires Ruby 2.7+)
- Rails 7.1 → Rails 7.2 or 8.0 (Requires Ruby 3.1+)
Test thoroughly at each step and check for breaking changes.
If Using Rails 7.0 Must complete upgrade before April 1, 2025. Target schedule:
- January-February 2025: Complete upgrade to 7.1 and stabilize
- March 2025: Complete upgrade to 7.2 or 8.0
If Using Rails 7.1 Upgrade needed before October 1, 2025. You have more time, so:
- June-August 2025: Upgrade to 7.2
- Or consider direct upgrade to 8.0 if it’s sufficiently stable
If Using Rails 7.2 or 8.0 Safe for now. Just apply regular patch updates.
7. If You Must Continue Using EOL Versions
Sometimes you may face situations where immediate upgrade is difficult due to legacy system characteristics. In such cases, consider the following options:
Use Commercial Support Services Companies like HeroDevs offer “Never-Ending Support (NES)” services. You can receive security patches and technical support for a fee even after EOL.
- Reference: HeroDevs Rails NES
Directly Manage Git Branches The Rails team may merge backports to x-y-stable branches even after EOL. You can point directly to the branch in Git to receive the latest fixes:
gem 'rails', github: 'rails/rails', branch: '7-0-stable'
However, this method has no official gem releases, so use cautiously in production environments.
Enhanced Security Measures
- Deploy Web Application Firewall (WAF)
- Regular security scans and penetration testing
- Strengthen network-level security
- Build monitoring systems
However, these methods are temporary measures. Long-term, you must upgrade to supported versions.
8. Useful Tools and Resources
Here are tools to help with Rails version management and upgrades:
Version Tracking Tools
- endoflife.date/rails: View EOL schedules for all Rails versions at a glance
- RubyGems Rails Versions: Complete Rails release history
Security Audit Tools
- Brakeman: Static security analysis tool for Rails applications
- bundler-audit: Check gem dependency security vulnerabilities
Upgrade Assistance Tools
- rails-upgrade-checklist: Version-specific upgrade checklists
- Ruby & Rails Compatibility Table: Ruby and Rails version compatibility matrix
Official Documentation
- Ruby on Rails Official Blog: Latest release news
- Rails Guides: Official guide documentation
- Rails API Documentation: API reference
Ruby Version Compatibility Reference Table
Ruby version must also be considered when upgrading Rails:
| Rails Version | Required Ruby | Recommended Ruby |
|---|---|---|
| 8.0.x | Ruby 3.2+ | Ruby 3.3 |
| 7.2.x | Ruby 3.1+ | Ruby 3.3 |
| 7.1.x | Ruby 2.7+ | Ruby 3.2 |
| 7.0.x | Ruby 2.7+ | Ruby 3.1 |
| 6.1.x | Ruby 2.5+ | Ruby 3.0 |
| 6.0.x | Ruby 2.5+ | Ruby 2.7 |
| 5.2.x | Ruby 2.2.2+ | Ruby 2.6 |
| 5.1.x | Ruby 2.2.2+ | Ruby 2.5 |
| 5.0.x | Ruby 2.2.2+ | Ruby 2.4 |
| 4.2.x | Ruby 1.9.3+ | Ruby 2.3 |
| 4.1.x | Ruby 1.9.3+ | Ruby 2.2 |
| 4.0.x | Ruby 1.9.3+ | Ruby 2.1 |
| 3.2.x | Ruby 1.8.7+ | Ruby 2.0 |
Note: Ruby also has its own EOL schedule, so check Ruby EOL dates at Ruby Maintenance Branches.
9. Final Thoughts – Check Now
Rails application version management isn’t just about “using the latest features”—it’s a critical issue directly tied to security and stability.
Check your current Rails version now and mark the EOL date on your calendar. It’s important to plan upgrades with plenty of lead time.
Check Current Version
rails -v
# or
bundle exec rails -v
# or check Gemfile.lock
cat Gemfile.lock | grep -A 1 "rails ("
Quick Reference: Key Dates for 2025
| Timeline | Action Required | Target Versions |
|---|---|---|
| Immediately | Urgent upgrade needed | Rails 6.1 and earlier (already EOL) |
| By March 2025 | Must complete upgrade | Rails 7.0 (EOL April 1) |
| By September 2025 | Plan upgrade | Rails 7.1 (EOL October 1) |
| Until August 2026 | Stable operation | Rails 7.2 |
| Until November 2026 | Stable operation | Rails 8.0 |
Complete Version History at a Glance
Rails 8.0 ━━━━━━━━━━━━━━━━━━━━━> 2026-11-07 EOL [Current Latest]
Rails 7.2 ━━━━━━━━━━━━━━━━━━━━━> 2026-08-09 EOL [Stable]
Rails 7.1 ━━━━━━━━━> 2025-10-01 EOL [Security Only]
Rails 7.0 ━━━> 2025-04-01 EOL [⚠️ Ending Soon]
Rails 6.1 ✕ 2024-10-01 EOL [Ended]
Rails 6.0 ✕ 2023-06-01 EOL
Rails 5.2 ✕ 2022-06-01 EOL
Rails 5.1 ✕ 2019-08-25 EOL
Rails 5.0 ✕ 2018-04-01 EOL
Rails 4.2 ✕ 2017-04-27 EOL
Rails 3.2 ✕ 2016-06-30 EOL
Key Summary
✅ New Policy (Rails 7.2+): Bug fixes 1 year + Security support 2 years
⚠️ Rails 7.0: EOL April 1, 2025 (Upgrade immediately)
🔔 Rails 7.1: EOL October 1, 2025 (Plan upgrade)
🔴 Rails 6.1 and earlier: Already EOL (Upgrade immediately required)
🎯 Latest Stable: Rails 8.0 (Full support until November 2026)
Regular Monitoring Checklist
- [ ] Check endoflife.date/rails quarterly
- [ ] Subscribe to Rails Official Blog
- [ ] Apply security patches within 24-48 hours of release
- [ ] Start planning upgrades 6 months before EOL
- [ ] Check Ruby version compatibility as well
Regularly check the official Rails blog and endoflife.date to stay updated. For safe and stable Rails application operations, plan and execute upgrades at the appropriate time! 🙂