Your next step 1 / 3

What are you working on?

Two quick choices. No technical brief needed.

The first conversation is free. No commitment to a paid service.

Apollo Tech Studio
Talk about your app

Guide · RubyUpdated October 9, 2026

Ruby end-of-life dates: which versions still get fixes

Ruby 3.2 reached end of life on April 1, 2026, and Ruby 3.3 is in security maintenance with an expected end of life of March 31, 2027. Ruby 4.0 and 3.4 are in normal maintenance with no end date set. This page lists every branch from ruby-lang.org and explains what each status means.

Explore at your own pace

Open the section you need. The detail and sources are there when you want them.

01

Ruby branches and status

From ruby-lang.org, “Ruby Maintenance Branches”, fetched October 9, 2026.

RubyStatusEnd of life
4.0Normal maintenanceTBD
3.4Normal maintenanceTBD
3.3Security maintenance2027-03-31 (expected)
3.2EOL2026-04-01
3.1EOL2025-03-26
3.0EOL2024-04-23
2.7EOL2023-03-31

The page lists older branches back to 1.9.3, all end of life. It says the shown dates are inferred from the English versions of release posts or EOL announcements.

02

What the statuses mean

Normal maintenance
“Branch receives general bug fixes and security fixes.” ruby-lang.org: Ruby Maintenance Branches
Security maintenance
“Only security fixes are backported to this branch.” ruby-lang.org: Ruby Maintenance Branches
EOL
“Branch is not supported by the ruby-core team any longer and does not receive any fixes.” ruby-lang.org: Ruby Maintenance Branches
Ruby 3.2
Status eol, end of life 2026-04-01. ruby-lang.org: Ruby Maintenance Branches
Ruby 3.3
Status security maintenance, end of life 2027-03-31 (expected). ruby-lang.org: Ruby Maintenance Branches
03

Ruby and Rails move together

A Rails upgrade often forces a Ruby upgrade, and the other way round. The Rails 8.0 end-of-life guide on this site lists the Ruby minimum for Rails 8.0 and 8.1, and Ruby 3.2 is already past its end of life.

If your app is on Ruby 3.2 or older, no further Ruby fixes will come. Plan the Ruby step with the Rails step, not after it.

04

What to check

  • Read .ruby-version, the Gemfile ruby line and the Dockerfile base image for the Ruby version you really run.
  • If it is 3.2 or older, there are no more Ruby fixes: schedule the upgrade.
  • If it is 3.3, plan the move before March 31, 2027 (expected).
  • Check that your gems support the target Ruby before you change production.
  • Upgrade Ruby and Rails in separate deploys so a failure points at one cause.
05

Questions about Ruby end of life

Is Ruby 3.2 end of life?

Yes. ruby-lang.org shows Ruby 3.2 as EOL since April 1, 2026.

When does Ruby 3.3 reach end of life?

ruby-lang.org shows 2027-03-31 as expected. It is in security maintenance now.

Which Ruby versions get bug fixes?

Ruby 4.0 and 3.4, both in normal maintenance with the end-of-life date still TBD.

Are these dates final?

The page says its dates are inferred from release posts and EOL announcements. Expected dates can move.

06

More deadlines

Next step

30 minutes with an engineer. Discuss your product, then get a free initial audit and a clear next step.

Show us what's stuck[email protected]

Sources

  1. ruby-lang.org: Ruby Maintenance Branches

Checked October 9, 2026.