EOL.Wiki EOL.Wiki
← ← Back to all products

ROS 2

Active
Other Latest Version: kilted Latest Release: N/A

ROS 2 is the next generation of the Robot Operating System with improved security and real-time support.

Versions

11

Latest Version

N/A

Active Support

3

EOL

8

Lifecycle Timeline

Today
kilted
kilted
jazzy
jazzy
iron
iron
humble
humble
galactic
galactic
foxy
foxy
eloquent
eloquent
dashing
dashing
crystal
crystal
bouncy
bouncy
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
kiltedMay 23, 2025-Dec 31, 2026-No
Active
jazzyMay 23, 2024-May 31, 2029-No
Active
ironMay 23, 2023-Dec 4, 2024-No
EOL
humbleMay 23, 2022-May 31, 2027-No
Active
galacticMay 23, 2021-Dec 9, 2022-No
EOL
foxyJun 5, 2020-Jun 20, 2023-No
EOL
eloquentNov 22, 2019-Nov 30, 2020-No
EOL
dashingMay 31, 2019-May 31, 2021-No
EOL
crystalDec 14, 2018-Dec 31, 2019-No
EOL
bouncyJul 2, 2018-Jul 31, 2019-No
EOL
ardentDec 8, 2017-Dec 31, 2018-No
EOL

Frequently Asked Questions

Which versions of ROS 2 have reached end of life?
The following ROS 2 versions have reached end of life and no longer receive security updates: iron, galactic, foxy, eloquent, dashing, crystal, bouncy, ardent. It is recommended to upgrade to a supported version.
Is it safe to continue using ROS 2 iron?
ROS 2 iron has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of ROS 2?
The latest version of ROS 2 is kilted, released in the kilted release cycle.
How many versions of ROS 2 are currently supported?
ROS 2 currently has 3 actively supported version(s): kilted, jazzy, humble.
When does ROS 2 kilted reach end of life?
ROS 2 kilted is scheduled to reach end of life on Dec 31, 2026.
What should I do when ROS 2 reaches end of life?
When a ROS 2 version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.