Robotics Lifecycle Intelligence

ROS Noetic Is EOL —
and ROS 1 ended with it.

Published 2026-06-11 · endoflife.ai · 5 min read

Quick answer: ROS Noetic Ninjemys — the final ROS 1 distribution — reached end of life in May 2025 (officially May 1, 2025, per the endoflife.date dataset), more than a year ago. Noetic was the last distribution of ROS 1 ever released, so its EOL didn't just retire a version: it ended the entire ROS 1 line. There are no further ROS 1 releases, no security patches, and no maintained migration window. The path forward is ROS 2.

If you run Noetic in production
Robots are long-lived assets — fleets routinely outlive the software they shipped with. A Noetic-based robot deployed today runs an unpatched middleware stack on an OS pairing (Ubuntu 20.04) that has itself left standard support. Both layers of that stack have stopped receiving fixes.

ROS 1 end-of-life timeline

DistributionReleasedEnd of LifeStatus
Kinetic KameMay 2016May 2021EOL
Lunar LoggerheadMay 2017May 2019EOL
Melodic MoreniaMay 2018Apr 2023EOL
Noetic NinjemysMay 2020May 2025EOL — final ROS 1 release

Live dates for every distribution are on the ROS lifecycle page, regenerated at every deploy.

What Noetic EOL actually means

End of life for Noetic means the ROS maintainers no longer publish updates of any kind: no security fixes, no bug fixes, no dependency rebuilds. Because Noetic targets Ubuntu 20.04 — which has also exited standard support — teams still on Noetic are accumulating unpatched CVEs at two layers simultaneously: the middleware and the operating system under it. This is the classic CVE blind spot: every vulnerability disclosed against either layer since EOL is public, documented, and permanently unfixed on your stack.

Migration: ROS 2 is the only forward path

With no ROS 1 successor, migration means moving to ROS 2 — current LTS distributions are supported on modern Ubuntu LTS releases with multi-year windows. The migration is real work: ROS 2 replaces the ROS 1 master/node architecture with DDS-based communication, and core APIs differ. Practical sequencing for most teams:

Track robotics stack EOL
ROS, Ubuntu, Python, and every other layer of a robotics stack have independent EOL clocks. Check any of them in the EOL Checker, or scan a full dependency file with the Stack Scanner.

The Monthly EOL Digest™

Once a month — critical end-of-life dates, CVE blind spots, and lifecycle changes worth knowing about.

✓ You're on the list.