If you’re still clinging to ROS 1 like a security blanket, I’ve got some news. It’s over. Well, almost. With the May 2025 EOL (End of Life) for Noetic officially in the rearview mirror, the community has fully pivoted. If you aren't tracking the latest ROS 2 news updates, you’re basically trying to program a Tesla with a hand crank.
The big story right now? Kilted Kaiju. Released in May 2025, this isn't just another incremental patch with a cute animal name. It represents a massive shift in how we handle robot communication, especially with the elevation of Zenoh to a Tier 1 middleware.
✨ Don't miss: Apple Watch and Bluetooth Headphones: What Most People Get Wrong
Honestly, the "DDS-only" days of ROS 2 felt a bit restrictive for some. Now, with Kilted Kaiju supported through November 2026, we’re seeing a landscape where "physical AI" isn't just a buzzword—it’s the architecture.
The Zenoh Revolution and Kilted Kaiju
For a long time, if you wanted to talk to a robot, you talked DDS. It worked, sure. But it could be a massive pain when you were dealing with spotty WiFi or low-bandwidth satellite links.
The biggest piece of ROS 2 news updates this year is the official Tier 1 support for Eclipse Zenoh.
💡 You might also like: What Really Happened With the Elon Musk and Trump Twitter Feud (and Where They Stand Now)
Why does this matter to you? Because Zenoh is significantly leaner. It doesn't have the discovery overhead that makes DDS crawl in complex networks. In Kilted Kaiju, Zenoh passed the full battery of SROS2 security tests—encryption, authentication, the whole nine yards. It's not the default yet, but it’s sitting there, ready for a "test drive" if you’re tired of your robot's heartbeat dropping every time it goes behind a concrete pillar.
Python isn't a second-class citizen anymore
We’ve all been there. You write a node in Python because it’s fast to prototype, and then you watch the CPU usage spike like a caffeine addict on a bender.
One of the most underrated ROS 2 news updates in the Kilted release is the EventsExecutor for rclpy.
- The Speed: We are talking benchmarks showing up to 10x speed improvements.
- The Type Checking: Better support for Python actions and generics (like
list[str]) means fewer "NoneType has no attribute" errors at 3 AM. - The Effort: You have to opt-in by using
rclpy.experimental.EventsExecutor, but the payoff is real.
Jazzy Jalisco: The Workhorse of 2026
While Kilted is the shiny new toy, Jazzy Jalisco is where the serious industrial work is happening. Supported until May 2029, it’s the Long Term Support (LTS) king.
In the latest 2026 syncs for Jazzy, we’ve seen some "hot-new" features in ros2_control that basically solve the "controller chaining" nightmare. You can now run complex cascade control or real-time state estimators without the jitter that used to plague complex mobile manipulators.
I saw a demo recently where a guy set up a mobile base and an arm using only configuration files—no extra C++ glue code. That’s the dream, right? Jazzy Jalisco finally makes that modularity feel stable rather than experimental.
🔗 Read more: Why Download Images of Instagram is Still a Massive Pain (and How to Actually Do It)
What’s happening with Lyrical Luth?
Looking ahead, the roadmap for Lyrical Luth (scheduled for May 2026) is already buzzing. The community is leaning hard into "Agentic AI."
What most people get wrong about ROS 2 is thinking it’s just a messaging system. It’s becoming an AI orchestrator. We’re seeing more "Retrieval-Augmented Generation" (RAG) pipelines specifically for ROS 2. Imagine asking your robot, "Hey, why did the nav stack fail three minutes ago?" and having an AI parse the logs and TF tree in real-time to give you an answer.
Real-World Impact: Cobots and Humanoids
The ROS 2 news updates aren't just about code; they're about the hardware hitting the floors.
- Comau’s MyCo: Just this month, Comau dropped their new line of cobots with ROS 2 support right out of the box.
- TARS ROS 2: Some absolute legend recreated the TARS robot from Interstellar using a ROS 2 stack. It’s not just a movie prop; it’s a functional AI-capable research platform.
- Phantom Bridge: This is a new web UI for monitoring that uses WebRTC. If you're tired of Rviz crashing over a remote connection, this is the observability tool you’ve been waiting for.
Why You Should Care About RMW Changes
If you’re still on Humble Hawksbill, you’re safe for now (it lives until May 2027), but the middleware shift is coming for everyone.
The move toward Iceoryx2 (v0.8.0) integration is another sleeper hit in recent news. It’s all about zero-copy communication. If you're passing high-res LIDAR clouds or 4K camera feeds between nodes, you cannot afford the overhead of serializing and deserializing that data. Iceoryx2 is making that local "talk" nearly instantaneous.
Actionable Steps for the ROS 2 Developer
Forget the "theoretical" stuff for a second. If you want to stay relevant in the 2026 robotics market, here is what you actually need to do:
- Audit your RMW: If you are struggling with network latency, don't just tweak DDS parameters. Try the Zenoh RMW in Kilted Kaiju.
- Switch to RQml: RQt is showing its age. The new RQml beta is a QML-based alternative that supports most existing plugins but feels like it belongs in this decade.
- Check your Python Executors: If your Python nodes are slow, migrate to the
EventsExecutor. It’s a literal one-line change in yourspincommand that can save your CPU. - Monitor the 2026 Roadmap: Keep an eye on the "Lyrical Luth" GitHub project board. If you have a feature you want to see, the OSRF is surprisingly responsive to community input right now.
The transition from ROS 1 to ROS 2 was painful, but the ecosystem we have now is infinitely more capable. Between the real-time performance of ros2_control and the networking flexibility of Zenoh, there’s never been a better time to be building. Just make sure you aren't building on an EOL distribution, or you'll be doing this all over again in six months.