Rails 8.0 end of life: 7 November 2026

What changes on 7 November 2026

Rails 8.0 was released on 7 November 2024. The Rails team published its support dates in advance: bug fixes until 7 May 2026 and security fixes until 7 November 2026, two years after release.

After 7 November 2026, the Rails maintenance policy is clear about what an unsupported series means: “it’s your own responsibility to deal with bugs and security issues”. Fixes may still appear in the Rails source, but no new Rails 8.0 versions are released.

In practice, three things change:

• Security advisories need your own judgement. When an advisory names Rails 8.0, there is no gem update to install. Someone has to assess whether the application is affected and patch it by hand, or upgrade.
• Dependency tools start to flag the application. Once an advisory affects Rails 8.0, Bundler Audit, Dependabot and similar tools report it, and the only fix they can offer is a newer series.
• Questions from customers get harder to answer. If a customer or an auditor asks whether your software runs on supported versions, the honest answer becomes no.

None of this makes the application fail overnight. It does mean that every month on 8.0 adds work the next time a security issue appears.

The step from 8.0 to 8.1

Rails 8.1 was released on 22 October 2025. Its headline features are optional: Active Job continuations, structured event reporting, a local CI runner, Markdown rendering and deprecated associations. An application does not have to use any of them to upgrade.

The removals are what need attention. Rails 8.1 removes a short list of things 8.0 had already deprecated, for example the :azure storage service in Active Storage, semicolons as a query-string separator, bin/rake stats and the SQLite3 adapter’s :retries option. It also deprecates the built-in Sidekiq adapter, which now comes with the sidekiq gem.

The official upgrade guide describes the method we follow:

1. Make sure the tests pass on the latest Rails 8.0 patch release.
2. Fix the deprecation warnings that release shows.
3. Change Rails to 8.1 in the Gemfile, run bundle update rails and then bin/rails app:update.
4. Run the tests, then turn on the new framework defaults one by one from config/initializers/new_framework_defaults_8_1.rb before setting config.load_defaults 8.1.

The new defaults can go out over several deploys, so each change is easy to trace if something behaves differently.

Check the Ruby version too

Rails 8.1 keeps the same Ruby minimum as 8.0, Ruby 3.2. That makes the Rails step simpler, but it hides a problem: Ruby 3.2 reached end of life on 1 April 2026. Ruby 3.3 receives security fixes only and is expected to reach end of life on 31 March 2027. Ruby 3.4 and 4.0 are in normal maintenance.

If the application runs on Ruby 3.2, upgrade Ruby and Rails as separate steps, each with its own deploy. Check that your gems support the Ruby version you choose before you start.

Before and after the date

Before 7 November 2026:

• Find the exact versions: rails in Gemfile.lock and the Ruby version in .ruby-version or the Gemfile.
• Move to the latest Rails 8.0 patch release and clear its deprecation warnings. This is useful work even if the upgrade itself waits.
• Check that the gems the application depends on have releases that support Rails 8.1.
• Decide when the 8.1 step happens and who does it.

If the application is still on 8.0 after the date, it keeps running. Follow the Rails security announcements, assess each advisory against the application, and plan the upgrade as soon as the work can be scheduled.

If the application is older than 8.0, the step to 8.1 is part of a longer path. The Rails end-of-life overview lists every series with its dates and minimum Ruby.