The ROSCon 2025 talks dropped this week and, buried in the release notes, the news that actually matters: ROS 2 Lyrical Luth is now the long-term release with support pledged through 2031, targeting Ubuntu 26.04 (Resolute) and Windows 11. A five-year promise from an open-source project is a load-bearing fact. It arrives the same month China unveiled OpenHarmony Robot OS for humanoids (per DigiTimes), the LeRobot Hub on Hugging Face crossed 58,000 community datasets — 50× growth in a year, per TechTimes — and the Boston Robotics Summit opened with one agenda question: open-source ROS versus proprietary physical AI.

←TODAY: ROS 2 Lyrical Luth ships in May 2026 with support until 2031, while OpenHarmony Robot OS launches in Beijing the same week.
→3012: By 3012, the robot fleet of a Swiss timber yard routes through three or four upstream software stacks — and the one that loses cooling, bandwidth, or maintainers vanishes overnight.
Fulcrum: Choosing a robot-software stack is a dependency-graph choice, and the time to draw the graph is before the first robot ships.

The dependency graph nobody draws

The architecture diagram of a robotics lab — KUKA arm, vision module, planner, controller — is the marketing version. The real picture is the dependency graph: which Python wheel pulls which CUDA build, which node subscribes to which topic at which QoS, which flag in a third-party message package gates whether your URDF parses on Ubuntu 26.04. ROS 2 is the lingua franca that makes this graph drawable, because every transport between nodes is a typed topic, service, or action — visible from the command line, auditable, replayable. That is what a five-year LTS actually buys: not feature stability, but stability of the graph you trained your team to reason about.

OpenHarmony’s pitch is that China needs a sovereign robotics OS for the humanoid wave; Forbes’ tech council reads the same wave as the moment robotics moves “from contained automation to open deployment.” Both observations imply the same engineering fact: more nodes, more vendors, more transports — and therefore more places where the dependency graph breaks silently. PAZ’s own Digital Twin concept panel makes the structural-engineering version of this argument: the twin earns its keep by staying synchronised, and the risk lives in the seams. Robotics is the same problem with motors.

What this changes on a DACH-academic desk this week

ETH’s Robotic Fabrication Lab, HSLU, and TU-Wien’s ACIN have been on ROS 1 or early ROS 2 for years; Lyrical Luth is the first release where committing a thesis project to the platform is defensible past the student’s PhD. If you are choosing a stack for an MAS project this autumn, the calculus is: ROS 2 LTS gets you to 2031, LeRobot’s 58k-dataset hub hands you ML baselines you no longer have to record yourself, and the cost is learning to read a publish-subscribe graph the way you used to read a Grasshopper canvas.

Atelier: In PAZ’s robotic-fabrication work — wood-jointing studies in the cohort, the curved-support ceramic-printing toolchain the ECAADe 2018 paper catalogued — the practical move is to pin Lyrical Luth as the project baseline and version every URDF, launch file, and message package as if it were a structural detail. The deliverable to a client is not the robot path. It is the reproducible graph that produced the path.

Hack: This Hack teaches you to print your robot’s actual publish-subscribe graph from the command line — the dependency graph, not the architecture diagram. Open a terminal on the machine your robot is running on, dump every live topic to a file, and ask one node what it publishes and subscribes to.

ros2 topic list --include-hidden-topics | sort > topics_live.txt
ros2 node info /your_node | grep -E "Publishers|Subscribers"
ros2 topic info /cmd_vel --verbose   # QoS, type, exact endpoints

Diff topics_live.txt against last week’s. The first time you find a node you did not know was running, you understand why the rule — draw the real dependency graph, not the architecture diagram — exists.

Install Lyrical Luth on a spare workstation this week, run the three commands above against your existing project, and put the diff into your project README. If the diff embarrasses you, that is the point.

Sources & Further Reading

• Primary: ROS — the Robot Operating System project
• Reinforcing: TechTimes — Humanoid Robots Reach Production Scale