ROS 2 distributions and end-of-life dates: Humble, Jazzy, Kilted, Lyrical
Choosing a ROS 2 distribution starts with knowing how long it will be supported. This page gathers the release and end-of-life (EOL) dates listed in the official ROS 2 release documentation.
Posez votre question
Compte gratuit requisLes réponses sont rédigées par un modèle de langage à partir des seuls documents de cette base, avec leurs sources numérotées. Elles peuvent être inexactes et ne constituent pas un conseil juridique, médical ou financier : vérifiez les sources avant toute décision importante.
Current distributions at a glance
Lyrical Luth was released on May 22, 2026. It is the twelfth ROS 2 release and a Long Term Support release, supported until May 2031.
Kilted Kaiju was released on May 23, 2025 with an end of life in December 2026. Jazzy Jalisco was released on May 23, 2024 and reaches end of life in May 2029. Humble Hawksbill was released on May 23, 2022 and reaches end of life in May 2027.
How the release cycle works
A new ROS 2 distribution is released every year on May 23rd, World Turtle Day. The next one, Makoa Mata-mata, is planned for May 2027 with a planned end of life in December 2028.
Once a distribution is released, changes to core packages are limited to bug fixes and non-breaking improvements, so developers can work against a stable codebase until they are ready to move forward.
Questions fréquentes
Which recent distributions are already end of life?
Iron Irwini reached end of life on December 4, 2024, Galactic Geochelone on December 9, 2022 and Foxy Fitzroy on June 20, 2023. They no longer receive updates.
Is Humble still supported?
Yes, Humble Hawksbill is listed with an end of life in May 2027. If you start a new project, Lyrical Luth offers a longer support window, until May 2031.
Who leads each release?
Each distribution has a ROS Boss. For Lyrical Luth it is Shane Loretz, for Kilted Kaiju Scott K Logan and for Jazzy Jalisco Marco A. Gutiérrez.
Intégrer / API / MCP
Branchez cette base à Claude, Cursor, ChatGPT ou votre propre application. Chaque requête API ou MCP coûte 0,10 €, débitée de votre crédit Kopik (non facturée si rien n'est trouvé). Il vous faut une clé API : créez-la depuis votre tableau de bord.
MCP pour vos agents
Adresse du serveur MCP de cette base (outils ask_base et search_base) :
https://kopik.io/api/mcp?base=ros2-robotics-documentationClaude Code, Cursor et autres clients
claude mcp add --transport http kopik-ros2-robotics-documentation "https://kopik.io/api/mcp?base=ros2-robotics-documentation" --header "Authorization: Bearer kpk_…"{
"mcpServers": {
"kopik-ros2-robotics-documentation": {
"url": "https://kopik.io/api/mcp?base=ros2-robotics-documentation",
"headers": {
"Authorization": "Bearer kpk_…"
}
}
}
}API REST pour vos applications
mode vaut "answer" (réponse rédigée + sources) ou "passages" (passages bruts seulement). Ajoutez un maxPriceCents facultatif pour plafonner le prix : si la base coûte plus cher, l'appel est refusé sans rien débiter.
curl -X POST https://kopik.io/api/v1/bases/ros2-robotics-documentation/query \
-H "Authorization: Bearer kpk_…" \
-H "Content-Type: application/json" \
-d '{"question": "Votre question ici", "mode": "answer"}'Pour commencer
- Créez une clé dans votre tableau de bord et rechargez votre crédit.
- Remplacez
kpk_…par votre clé. - Tout le détail (réponses, erreurs, exemples JS et Python) : documentation développeurs.