Ruby

Ruby

Language

Ruby 4.0 is the newest actively maintained release, currently at patch 4.0.9. 3 of 16 tracked cycles remain supported. The next cycle scheduled to reach end-of-life is 3.3, on March 31, 2027.

Latest version

4.0.9

Oct 22, 2026

Actively maintained cycles

3

of 16 tracked

Total cycles tracked

16

since Aug 4, 2003

Support pattern

How Ruby has behaved across the cycles tracked here, rather than what its policy documents state. Useful for judging how much runway a version is likely to have before you commit to it.

Typical support window

39 mo (~3.3 years)

median of 16 completed cycles

New cycle roughly every

12 months

median gap between releases

Compared with language

+18 mo

longer than the language median

Next end of life

131 days

Ruby 3.3

Support windows have stayed consistent across the tracked history, so past cycles are a reasonable guide to what a new one will get.

Computed from release and end-of-life dates tracked for Ruby. Medians are used rather than averages so one unusually short or long release does not skew the figure. Cycles with no recorded end-of-life date are excluded from the support window.

How Ruby versioning, EOL & security support work

Ruby releases a new major or minor version annually, on December 25th, and tracks each branch's support status on its official branches page. Each branch moves through named phases, normal maintenance, then security maintenance, before being marked end of life.

Normal maintenance: actively maintained

A newly released branch starts in normal maintenance, receiving general bug fixes and security fixes. This is the fullest level of support a Ruby branch gets.

Security maintenance: security support only

Once normal maintenance ends, a branch moves into security maintenance, where only security fixes are backported. General bug fixes are no longer applied.

End of life: no fixes at all

After security maintenance, a branch is marked EOL: not supported by the ruby-core team any longer and not receiving any fixes, security or otherwise.

Ruby vulnerabilities are reported privately, either through Ruby's HackerOne program or by email to [email protected], specifically not through the public bug tracker. The security team fixes confirmed issues, ships a patch release, and only then publishes details. Since fixes are only backported to branches still in normal or security maintenance, a branch already marked EOL receives nothing for any vulnerability found afterward.

Sources: Ruby Maintenance Branches, Ruby Security page

Release lifecycle

Actively maintainedSecurity support onlyEnd of life
Today
4.0Latest
4.0.9 · Oct 22, 2026
3.4
3.4.12 · Oct 23, 2026
3.3
3.3.13 · Oct 23, 2026
3.2
EOL Mar 31, 2026
3.1
EOL Mar 26, 2025
3.0
EOL Apr 23, 2024
2.7
EOL Mar 31, 2023
2.6
EOL Mar 31, 2022
2.5
EOL Mar 31, 2021
2.4
EOL Mar 31, 2020
2.3
EOL Mar 31, 2019
2.2
EOL Mar 31, 2018
2.1
EOL Mar 31, 2017
2.0.0
EOL Feb 24, 2016
1.9.3
EOL Feb 23, 2015
1.8
EOL Jun 30, 2013
200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027

Get an email when Ruby ships a release, announces an end-of-life date, or moves a date it already announced.

Get Ruby alerts