> ## Content Index > Fetch the complete content index at: https://stackurity.ai/blog/llms.txt > Use this file to discover other available public pages before exploring further. # Ruby on Rails 8.0 end of life: dates and how to upgrade - URL: https://stackurity.ai/blog/rails-8-0-end-of-life/ - Published: 2026-11-02T02:05:05.000Z - Updated: 2026-11-02T02:05:04.000Z - Description: Ruby on Rails 8.0 reaches end of life on November 7, 2026. See which applications are affected, how to check one and how to plan the upgrade. - Author: Stackurity Research Team - Tags: Open Source Libraries, #deep-dive ## TL;DR - Ruby on Rails 8.0 reaches end of life on November 7, 2026, five days from today, according to endoflife.date. - The support phase for the line already ended on May 7, 2026, so the line has been in its final stretch for months. - After end of life, new vulnerabilities in Rails itself will not get fixes in this release line, and your application inherits that risk. - The latest release in the line is 8.0.5.1: update to it now, then plan the move to a supported Rails release. - Stackurity matches end-of-life data against your inventory every day, so applications still on this line show up in a short list. ## What reaches end of life, in plain English Ruby on Rails is a web application framework. Each release line, such as Ruby on Rails 8.0, is maintained for a limited period. While a line is maintained, the Rails maintainers publish fixes for bugs and security problems. When it reaches end of life, that stops. Nobody ships a patch release for the line, even if a serious flaw turns up the week after. The [endoflife.date record for Rails](https://endoflife.date/rails) tracks several dates for each line. For Ruby on Rails 8.0 it shows a release date of November 7, 2024, the end of the support phase on May 7, 2026, and the end of life on November 7, 2026\. The record lists no extended support period and marks the line as not a long term support release. In practice that means November 7, 2026 is the hard stop: there is no paid or community extension to rely on in this record. It helps to be precise about the two dates. The support phase is the period in which the maintainers still treat the line as actively looked after. The end of life date is the point after which the line is no longer maintained at all. You are already past the first date, and the second is days away. ## Why it matters now Framework end of life is easy to ignore because nothing breaks on the day. Your application keeps serving pages. What changes is what happens the next time a vulnerability is reported in Rails, its request handling or its bundled components. For a supported line, a fix appears and you update. For a line past end of life, the fix goes to newer lines only, and you have to move to one of those under pressure, often together with a flaw that attackers are already trying. There is a second, quieter cost. Auditors and customers ask which components in your stack are still supported. An application on an unmaintained framework is a finding that needs an exception, a compensating control or an upgrade plan. It is much cheaper to have the upgrade scheduled before the date than to explain afterwards why it was not. Framework upgrades also take time. Moving between Rails release lines can touch deprecated methods, gems that pin an older Rails, configuration defaults and the Ruby version you run. Five days is not enough to finish a careful upgrade of a large application, but it is enough to find every application on the line, update to the latest patch release and put dates on the rest. ## Am I affected? You are affected if any application you run uses the Ruby on Rails 8.0 release line, whether in production, staging or a background worker. The release line is the first two parts of the version number. Any version that begins with the cycle shown in the record belongs to it, up to the latest release, 8.0.5.1. To check one application by hand, run these from the application directory: ``` bundle exec rails -v bin/rails about bundle list | grep rails grep -E '^ rails \(' Gemfile.lock ``` The first command prints the Rails version the application actually loads. The second prints a summary that includes the Rails version and the Ruby version. The last two read your installed gems and the lockfile, which is the source of truth for what gets deployed. Check every environment, since a staging server or a scheduled job can lag behind production. One caveat applies to frameworks installed as gems: distributions do not backport fixes into your application's bundle the way they do for system packages. The version in your Gemfile.lock is the version you run, so the end of life date applies to you directly, with no distribution patch to lean on. If a Linux distribution package ships Rails for you, read that vendor's notice instead of relying on the upstream date alone. ## How to upgrade away from Ruby on Rails 8.0 1. Find every application on the line. Search lockfiles in all repositories for a Rails entry from the 8.0 line, and list each deployed application with its environment and owner. 2. Update each one to 8.0.5.1, the latest release in the line, run the test suite, and deploy. This keeps you on the most recently patched code while you plan the larger move. 3. Choose the supported Rails release you will move to. The records we use here do not list the next release, so read the maintenance policy on the Rails site for the current supported lines and pick one that all your key gems support. 4. Upgrade in the steps the Rails guides describe, fix deprecation warnings as you go, and confirm the Ruby version you run is supported by the target release. 5. Re-read the lockfile after the deploy and confirm the new Rails version is the one that is loaded, then remove any temporary exceptions you created. If a full upgrade cannot land before November 7, 2026, record the exception with an owner and a date, limit exposure of the application while you work, and keep the update to 8.0.5.1 in place. For help planning fixes in order of urgency, see how Stackurity [turns findings into upgrade cards](https://stackurity.ai/docs/remediation). ## How to check with Stackurity Stackurity keeps one live inventory of the software on your servers, deployed applications and repositories. A read-only agent on Linux servers reads the libraries that deployed applications actually load, and repositories can be added from their lockfiles, including RubyGems. End-of-life data is matched against that inventory every day, so an application on a release line that is about to leave support appears in a short list, most urgent first, alongside the vulnerabilities that matter more. After you upgrade, check again asks the agent for a fresh report and records whether the issue is really gone, so you can see the old line disappear instead of assuming the deploy worked. Read how [verification](https://stackurity.ai/docs/verification) works. The core is open source, and Stackurity Cloud offers a 14-day free trial without a card: [start a free trial](https://app.stackurity.dev/signup?utm%5Fsource=blog&utm%5Fmedium=referral&utm%5Fcampaign=open-source-libraries&utm%5Fcontent=rails-8-0-end-of-life). If you track other platforms that are leaving support, our guides on [RHEL 8 end of life](https://stackurity.ai/blog/rhel-8-end-of-life/) and [Windows Server end of life dates](https://stackurity.ai/blog/windows-server-2016-end-of-life/) cover the operating systems underneath your applications. ## FAQ ### When does Ruby on Rails 8.0 reach end of life? The endoflife.date record for Ruby on Rails 8.0 gives November 7, 2026 as the end of life date. After that date the release line is no longer maintained, so new vulnerabilities will not be fixed in it. ### Is Ruby on Rails 8.0 still getting security updates? Until November 7, 2026 it is still inside its end of life window. The record shows that the support phase ended on May 7, 2026, so treat the line as in its final stretch and plan the move now. ### What is the latest Ruby on Rails 8.0 release? The endoflife.date record lists 8.0.5.1 as the latest release in the line. Update to it first if you are on an older patch, then plan the move to a supported Rails release. ### How do I find which applications run Ruby on Rails 8.0? Read each application's Gemfile.lock for the rails line, or run the version command inside the application. Across many repositories, an inventory that reads lockfiles saves you from opening each one by hand. ### What should I upgrade Ruby on Rails 8.0 to? Move to a Rails release that is still supported by the Rails maintainers. Check the maintenance policy on the Rails site for the current list, and run your test suite on each step of the upgrade. Sources: [endoflife.date, Ruby on Rails](https://endoflife.date/rails) and [Stackurity product facts](https://stackurity.ai/llms.txt).