Skip to content

feat(msgs): vendor 11 standard ROS 2 packages for Jazzy coverage#195

Open
vihaan-kovari wants to merge 3 commits into
ZettaScaleLabs:mainfrom
Kovari-Industries:feat/expand-msg-coverage
Open

feat(msgs): vendor 11 standard ROS 2 packages for Jazzy coverage#195
vihaan-kovari wants to merge 3 commits into
ZettaScaleLabs:mainfrom
Kovari-Industries:feat/expand-msg-coverage

Conversation

@vihaan-kovari
Copy link
Copy Markdown

@vihaan-kovari vihaan-kovari commented Jun 2, 2026

Description

  • Vendor 11 additional standard ROS 2 message packages
  • Fix hiroz-codegen action parser to handle empty Result/Feedback sections (matching ROS 2 / rosidl semantics). Example of this is tf2_msgs/LookupTransform.action, which has an empty feedback section.

The messages added are:

  • From ros2/common_interfaces: diagnostic_msgs, shape_msgs, stereo_msgs, trajectory_msgs, visualization_msgs, std_srvs
  • From ros2/rcl_interfaces: rosgraph_msgs, statistics_msgs, composition_interfaces
  • From ros2/geometry2: tf2_msgs
  • From ros/rosbag2: rosbag2_interfaces

Vendors every remaining interface package from ros2/common_interfaces, ros2/rcl_interfaces, ros2/geometry2, and ros2/rosbag2, bringing Jazzy coverage of these four repos to 100%.

This PR overlaps with #191 on tf2_msgs vendoring, but adds all tf2_msgs.

Checklist

  • Ran ./scripts/check-local.sh successfully
  • Added/updated tests/documentation (if applicable)

External contributors: Please open as draft initially. See CONTRIBUTING.md.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jun 2, 2026

CLA assistant check
All committers have signed the CLA.

@vihaan-kovari vihaan-kovari changed the title Feat/expand msg coverage feat(msgs): vendor 11 standard ROS 2 packages for Jazzy coverage Jun 2, 2026
@vihaan-kovari vihaan-kovari marked this pull request as ready for review June 2, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants