Ruby End of Life: Supported Versions and EOL Dates
Three Ruby versions are supported today: 4.0 and 3.4 get normal maintenance, and 3.3 gets security fixes only until 31 March 2027. Ruby 3.2 reached end of life on 1 April 2026.
2 yr 4 mo left
Ruby 4.0 gets security updates until 31 Mar 2029 (2 yr 4 mo left). This date is our estimate: Ruby has not announced dates for this branch; recent branches got normal maintenance until 1 April and security fixes until 31 March, about 2 and 3 years after their 25 December release, so we apply the same pattern.
A new Ruby version ships every 25 December. Each branch usually gets about two years and three months of normal maintenance, then security fixes until about three years and three months after release.
The newest release is Ruby 4.0, released on 25 December 2025. Ruby 4.1 is in preview.
Ruby lists end dates as TBD for the newest branches. For those we apply the pattern of recent branches and mark the dates as estimates.
The latest releases are 4.0.9, 3.4.12 and 3.3.13. Run ruby -v to see which version you have. If you are on 3.3, plan an upgrade before March 2027. Ruby 4.0 is a normal yearly release despite the new major number, and most 3.4 code runs on it with few changes.
Ruby support dates
| Version | Released | Normal maintenance | Security maintenance (EOL) | Time left | Status | Latest |
|---|---|---|---|---|---|---|
| Ruby 4.0 | Estimated[1] | Estimated[1] | 2 yr 4 mo left | Supported | 4.0.9 | |
| Ruby 3.4 | Estimated[1] | Estimated[1] | 1 yr 4 mo left | Supported | 3.4.12 | |
| Ruby 3.3 | Official[1] | Official[1] | 4 mo left | Security fixes only | 3.3.13 | |
| Ruby 3.2 | Official[1] | Official[1] | Ended | Unsupported | 3.2.11 | |
| Ruby 3.1 | Official[1] | Official[1] | Ended | Unsupported | ||
| Ruby 3.0 | Official[1] | Official[1] | Ended | Unsupported | ||
| Ruby 2.7 | – | Ended | Unsupported | |||
| Ruby 2.6 | – | Official[1] | Ended | Unsupported | ||
| Ruby 2.5 | – | Official[1] | Ended | Unsupported | ||
| Ruby 2.4 | – | Ended | Unsupported | |||
| Ruby 2.3 | – | Ended | Unsupported | |||
| Ruby 2.2 | – | Ended | Unsupported | |||
| Ruby 2.1 | – | Ended | Unsupported | |||
| Ruby 2.0.0 | – | Ended | Unsupported | |||
| Ruby 1.9.3 | – | Ended | Unsupported |
Official published by the vendor · Confirmed observed (for example, patches stopped) · Estimated our forecast, with the rule stated · How we date things
Timeline
Normal maintenanceSecurity maintenance (EOL)Extended supportEstimatedEnded
What happens when support ends
Will it still run?
Your Ruby programs keep running. Nothing in Ruby stops working at end of life.
Will it get security fixes?
The Ruby core team publishes no more releases for that branch, even for security flaws.
What stops working?
Gems drop support for old Ruby versions, and new Rails releases require newer Ruby. Hosting platforms remove old Ruby runtimes.
What are my options?
- Move to Ruby 3.4 or 4.0.
- Use a version manager such as rbenv or asdf to test a new version first.
- Run your test suite with deprecation warnings turned on before upgrading.
What to do
Run ruby -v to see your version. Install a newer Ruby with rbenv, asdf or your package manager, then run bundle install and your tests.
Ruby versions: end of support, one by one
Ruby 4.0 end of life Supported
Ruby 4.0 gets security updates until 31 Mar 2029 (2 yr 4 mo left). This date is our estimate: Ruby has not announced dates for this branch; recent branches got normal maintenance until 1 April and security fixes until 31 March, about 2 and 3 years after their 25 December release, so we apply the same pattern. Current stable branch. Ruby lists its end dates as TBD.
Ruby 3.4 end of life Supported
Ruby 3.4 gets security updates until 31 Mar 2028 (1 yr 4 mo left). This date is our estimate: Ruby has not announced dates for this branch; recent branches got normal maintenance until 1 April and security fixes until 31 March, about 2 and 3 years after their 25 December release, so we apply the same pattern.
Ruby 3.3 end of life Security fixes only
Ruby 3.3 gets security fixes only, until 31 Mar 2027 (4 mo left). Normal maintenance ended on 1 Apr 2026.
Ruby 3.2 end of life Unsupported
Ruby 3.2 stopped getting security updates on 1 Apr 2026 and is no longer supported.
Ruby 3.1 end of life Unsupported
Ruby 3.1 stopped getting security updates on 26 Mar 2025 and is no longer supported.
Ruby 3.0 end of life Unsupported
Ruby 3.0 stopped getting security updates on 23 Apr 2024 and is no longer supported.
Ruby 2.7 end of life Unsupported
Ruby 2.7 stopped getting security updates on 31 Mar 2023 and is no longer supported.
Ruby 2.6 end of life Unsupported
Ruby 2.6 stopped getting security updates on 12 Apr 2022 and is no longer supported.
Ruby 2.5 end of life Unsupported
Ruby 2.5 stopped getting security updates on 5 Apr 2021 and is no longer supported.
Ruby 2.4 end of life Unsupported
Ruby 2.4 stopped getting security updates on 31 Mar 2020 and is no longer supported.
Ruby 2.3 end of life Unsupported
Ruby 2.3 stopped getting security updates on 31 Mar 2019 and is no longer supported.
Ruby 2.2 end of life Unsupported
Ruby 2.2 stopped getting security updates on 31 Mar 2018 and is no longer supported.
Ruby 2.1 end of life Unsupported
Ruby 2.1 stopped getting security updates on 17 Mar 2017 and is no longer supported.
Ruby 2.0.0 end of life Unsupported
Ruby 2.0.0 stopped getting security updates on 24 Feb 2016 and is no longer supported.
Ruby 1.9.3 end of life Unsupported
Ruby 1.9.3 stopped getting security updates on 23 Feb 2015 and is no longer supported.
For businesses and auditors
Paste this into a risk register, an audit response or an insurance questionnaire. It updates with the version picked above.
As of 22 Nov 2026: Ruby 4.0 gets security updates until 31 Mar 2029 (2 yr 4 mo left). This date is our estimate: Ruby has not announced dates for this branch; recent branches got normal maintenance until 1 April and security fixes until 31 March, about 2 and 3 years after their 25 December release, so we apply the same pattern. Source: https://www.itechtics.com/eol/ruby/, verified 11 Nov 2026.Get Ruby end-of-life alerts
We email you 90, 30 and 7 days before a Ruby version loses support, and when a vendor moves a date. One email at most per day, unsubscribe in one click.
Prefer your calendar? Add Ruby end dates to your calendar (subscribe to the link in Outlook, Google or Apple Calendar).
Ruby core team support policy
Ruby ships one release a year, on 25 December. Each branch gets normal maintenance for about two years and three months, then security maintenance until about three years and three months after release.
What changed
- Ruby 1.9.3 · Released: 30 Oct 2011 → 31 Oct 2011
- Ruby 2.5 · Security updates until: 31 Mar 2021 → 5 Apr 2021
- Ruby 3.0 · Security updates until: 31 Mar 2024 → 23 Apr 2024
- Ruby 2.6 · Security updates until: 31 Mar 2022 → 12 Apr 2022
- Ruby 3.2 reached end of support.
- Ruby 4.0 was released.
Frequently asked questions
Which Ruby versions are still supported?
As of 22 Nov 2026, these Ruby versions get security updates: Ruby 4.0, Ruby 3.4, Ruby 3.3.
When does Ruby 4.0 support end?
Ruby 4.0 gets security updates until 31 Mar 2029 (2 yr 4 mo left). This date is our estimate: Ruby has not announced dates for this branch; recent branches got normal maintenance until 1 April and security fixes until 31 March, about 2 and 3 years after their 25 December release, so we apply the same pattern.
What happens when Ruby reaches end of life?
Your Ruby programs keep running. Nothing in Ruby stops working at end of life. The Ruby core team publishes no more releases for that branch, even for security flaws.
Which Ruby versions are supported?
Ruby 3.3, 3.4 and 4.0. Ruby 3.3 gets security fixes only.
When does Ruby 3.3 reach end of life?
Ruby expects 31 March 2027.
Is Ruby 3.2 still supported?
No. Ruby 3.2 reached end of life on 1 April 2026. The last release was 3.2.11.
When does Ruby 3.4 reach end of life?
Ruby has not announced it yet. Based on past branches, we expect March 2028.
How do I check my Ruby version?
Run ruby -v.
Sources and method
Dates come from the vendor's own lifecycle pages wherever they exist and are checked against them on a schedule. A date is Official when the vendor publishes it, Confirmed when we have seen the updates stop, and Estimated when the vendor publishes nothing and we forecast it from their past behaviour. The rule is shown next to every estimate. Status and time left are worked out from today's date.
Spotted a wrong date? Tell us and include the source.