ci: swap Rolling for Lyrical Luth (Ubuntu 26.04) across matrix and docs#405
Open
bburda wants to merge 3 commits into
Open
ci: swap Rolling for Lyrical Luth (Ubuntu 26.04) across matrix and docs#405bburda wants to merge 3 commits into
bburda wants to merge 3 commits into
Conversation
ROS 2 Lyrical Luth is the new LTS released May 2026, supported until May 2031, targeting Ubuntu 26.04 Resolute Raccoon (Python 3.14, gcc 15, rclcpp 32). Drop the Rolling matrix entry in favour of Lyrical so all three tested distros are LTS. CI matrix: rolling/noble -> lyrical/resolute in ci.yml, docker-publish.yml, opcua-plugin.yml. Jazzy/noble and Humble/jammy entries unchanged. ROS2MedkitCompat.cmake docstrings extended to cover Lyrical (rclcpp 32+, yaml_cpp_vendor target export, ament_target_dependencies removal in ament_cmake 2.8.5+). Runtime detection already handles the new distro; no logic change needed. Docs (README, CONTRIBUTING, QUALITY_DECLARATION, installation, troubleshooting, tutorials, copilot-instructions, cmake/gateway design docs) updated with correct Ubuntu codename pairings (Resolute=26.04, Noble=24.04, Jammy=22.04). C++ comments and source comments swapped Rolling -> Lyrical where the behaviour carries forward; historical attribution preserved as "on Lyrical (originally observed on Rolling)" or "Rolling/Lyrical" where the bug was first reproduced on Rolling. snapshot_capture.cpp C++20 aggregate-init comment updated for gcc 15 (Lyrical). closes #404
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Summary
Swap our Rolling CI matrix entry for the freshly-released Lyrical Luth LTS (May 2026, Ubuntu 26.04 Resolute Raccoon, supported until May 2031). Test against a stable LTS instead of a moving target. Jazzy and Humble entries unchanged.
The change spans CI workflows, the multi-distro CMake compat module, all user-facing docs, and source comments that name a specific distro for historical bug context.
Issue
Type
Testing
ubuntu:resolute+ros-tooling/setup-ros@v0.7(the floating tag resolves to v0.7.18 which added Lyrical in v0.7.16). Watch the newbuild-and-test (lyrical, ubuntu:resolute)andDocker Publish (lyrical)jobs.ubuntu:resoluteDocker tag exists on Docker Hubros:lyrical-ros-baseDocker tag existspackages.ros.org/ros2/ubuntu/dists/resolute/existsros-lyrical-rclcpp= 32.0.0 (compat module's>= 21check still passes)ros-lyrical-rosbag2-storage= 0.33.3 (>= 0.22, no old-timestamp shim)libcpp-httplib-devon Resolute = 0.26 (pkg-config branch succeeds)ament_target_dependenciesremoved inament_cmake2.8.5+ (Lyrical ships 2.8.7) - runtime fallback inmedkit_target_dependenciestakes the explicit-targets pathChecklist
ros2_medkit-rolling:latestDocker tag should switch toros2_medkit-lyrical:latest; the old tag stops receiving updates after this lands)Notes for reviewers
--skip-keys ament_cmake_clang_format ament_cmake_clang_tidyrationale was reworded acrossci.yml+opcua-plugin.yml+ 8CMakeLists.txtfiles: the previous comments claimed the keys "were not registered" on certain distros, but verification againstrosdistroshows both keys are registered on Humble + Lyrical. Honest rationale is now "linters only run in the Jazzy quality job, defensive against transient binary-deb gaps on newly-released distros".QUALITY_DECLARATION.mdno longer claims Lyrical is Tier 1 per REP-2000 - REP-2000 hasn't been updated to list Lyrical yet.