Ruby 3.4 End of Life
Support dates, the patch stream you lose at EOL, and upgrade guidance — rebuilt from live data.
Ruby 3.4 is actively supported. It reaches end of life on 31 Mar 2028.
Support timeline
Official dates from the Ruby release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 24 Dec 2024 | — |
| End of life (scheduled) | 31 Mar 2028 | in 600 days |
| Latest release | 3.4.10 · 30 Jun 2026 | current |
What you lose on 31 Mar 2028
Being supported means fixes keep shipping to this branch. Here is the stream that stops. Source: NVD.
Ruby CVEs published and patched, by year
1 published in the last 12 months · data refreshed 2026-08-09
At the last-12-month rate of 1 Ruby CVEs, running 3.4 for a year past 31 Mar 2028 means roughly that many vulnerabilities fixed upstream but never backported to your branch. Past branches bear this out: Ruby 3.2 has missed 1 since it went end of life.
How much runway a newer branch buys
Moving to Ruby 4.0 extends security support by about 365 days.
| Branch | End of life | Days left | vs 3.4 |
|---|---|---|---|
| Ruby 4.0 | 31 Mar 2029 | 965 | +365 days |
| Ruby 3.4 | 31 Mar 2028 | 600 | this branch |
| Ruby 3.3 | 31 Mar 2027 | 234 | -366 days |
Review ruby-lang.org before moving to Ruby 4.0.
Frequently asked questions
When does Ruby 3.4 reach end of life?
Ruby 3.4 reaches end of life on 31 Mar 2028 — 600 days from now. After that date it receives no security fixes.
Is Ruby 3.4 still supported?
Yes. Ruby 3.4 is currently maintained. Latest release: 3.4.10, published 30 Jun 2026.
What happens when Ruby 3.4 reaches end of life?
Security fixes stop. Over the last 12 months 1 Ruby vulnerabilities were published and patched across supported branches; once 3.4 is end of life, fixes at that rate no longer reach it.
How long do I have to upgrade from Ruby 3.4?
600 days. Moving to Ruby 4.0 instead buys roughly 365 more days of security support.