Current participants as of December 10, 2024 08:12 AM (UTC):
ASL ETHZ, Achu Wilson, CAR: Components, Agents, and Robots with Dynamic Languages, David Hodo, Fawkes, Isaac Saito, John Stowers, Mat Sadowski Blog, Michael Ferguson, MobileWill, MoveIt!, NooTriX, Open Source Robotics Foundation, PAL Robotics blog, Pi Robot, ROS Discourse General, ROS Industrial, ROS news, ROSVirtual, Robbie The Robot, Robots For Robots, Sachin Chitta's Blog, TORK, William Woodall, Yujin R&D, mobotica,

Want your blog to be on the awesome planet ROS ?

If you are a ROS developer/user and you blog about it, ROS wants those contributions on this page ! All you need for that to happen is:

• have an RSS/Atom blog (no Tweeter/Facebook/Google+ posts)
• open a pull request on planet.ros tracker indicating your name and your RSS feed/ATOM url. (You can just edit the file and click "Propose File Change" to open a pull request.)
• make your ROS related posts tagged with any of the following categories: "ROS", "R.O.S.", "ros", "r.o.s."

Warnings

For security reasons, html iframe, embed, object, javascript will be stripped out. Only Youtube videos in object and embed will be kept.

Guidelines

Planet ROS is one of the public faces of ROS and is read by users and potential contributors. The content remains the opinion of the bloggers but Planet ROS reserves the right to remove offensive posts.

Blogs should be related to ROS but that does not mean they should be devoid of personal subjects and opinions : those are encouraged since Planet ROS is a chance to know more about ROS developers.

Posts can be positive and promote ROS, or constructive and describe issues but should not contain useless flaming opinions. We want to keep ROS welcoming :)

ROS covers a wide variety of people and cultures. Profanities, prejudice, lewd comments and content likely to offend are to be avoided. Do not make personal attacks or attacks against other projects on your blog.

Suggestions ?

If you find any bug or have any suggestion, please file a bug on the planet.ros tracker.

Dear ROS Community,

It is bitter-sweet to announce that ROS 2 Iron Irwini is now end-of-life.

Iron Irwini was released on May 23rd 2023 and marked the ninth distribution of ROS 2. Despite being a non-LTS release, it was feature packed (see more).

Over the past year and half, there have been 40 distro syncs and 7 patch releases that cumulatively brought thousands of packages and updates to the community.

The last patch and sync (tagged iron/2024-12-04) brought 6 new packages and 320 updates.

Expand for details of the final sync (click for more details)

The distribution has been marked end-of-life across docs.ros.org, index.ros.org and rosdistro. CI and Buildfarm jobs have been disabled and will be deleted after a month assuming no issues crop up. The final snapshot of the distribution has been uploaded to snapshots.ros.org. If you are currently using Iron, please switch to Jazzy Jalisco which is the latest LTS release. The transition should be very smooth.

It has been a great privilege of mine to serve as the ROS Boss for Iron Irwini especially given that Steve Irwin was my childhood hero. A big thank you to all ROS maintainers and community members for making Iron Irwini such a successful release!

-Yadu

1 post - 1 participant

Read full topic

Please come and join us for this coming meeting at 1700-1800 UTC on Monday 16th December 2024, where Tomoya Fujita will be talking about Robotics Platforms empowered by Cloud-Native Technologies.

Tomoya is a software engineer, contributor to ROS2 core, and well-respected community builder. In this session, he will talk about a range of Cloud-Native Technologies he has worked on, and their relevance to robotics. In particular, Tomoya has done a great deal of work on KubeEdge, a platform built on Kubernetes that can be used to deploy software to robots as if they are Kubernetes clusters. Some resources from his talk includes:

• ROSCon 2023: ROS with Kubernetes / KubeEdge
• Some examples to deploy ROS / ROS 2 with Kubernetes
• Next-generation Robotics Platform for Edge/Cloud

Tomoya also plans to leave time to discuss Cloud Robotics with the group, particularly the problems that people are having with Cloud Robotics.

Last meeting, we worked through a workshop for Eclipse Zenoh to test its capabilities and ease of setup. If you’re interested to see our progress, please check the meeting recording.

If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on YouTube with our other meeting recordings too!

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

Robotics engineers are in high demand — but what is the job really like?

2 posts - 1 participant

Read full topic

ROS News for the Week of December 2nd, 2024

ROSCon Germany and ROSCon India were both this week! It was really exciting to see two ROS events happening concurrently on two different parts of the globe. We want to congratulate the organizers and attendees on putting together fantastic events.

• ROSCon India photo from @purushottamshet on Twitter
• ROSCon Germany photo from @stoglrobotics on Twitter

But wait, there’s more! Our first ever ROSCon China in Shanghai is about to kick off in about four or five hours.

While we’re welcoming so many new friends to the ROS community we’re also getting ready to say farewell to ROS 1 Noetic, Gazebo Classic, Gazebo Citadel, and ROS 2 Iron Irwini.

We have two ROS Meetups planned for 2024-12-12. One meetup in Singapore and another one in Barcelona Spain

If you are in a giving mood this holiday season we are currently running a donation campaign for the OSRF. We’ve made it possible for you to earmark your donation for particular OSRF projects like the ROS Build Farm, the ROS Documentation, and our educational outreach initiatives.

At last week’s Gazebo Community Meeting we met multiple competitors from the NASA SpaceROS Summer Sprint Challenge. The results are absolutely amazing and are all open source! We recommend you check it out.

Events

• Looking for Austin ROS Meetup Speakers!
• 2024-12-07 Circuit Launch Mountain View Grand Opening
• 2024-12-07 → 2024-12-08 ROSCon China in Shenzhen
• 2024-12-10 ROS 2 Rust Meeting: December 2024
• 2024-12-11 => 2024-12-12 Humanoids Summit Bay Area
• 2024-12-11 Embodied AI Community Group meeting 2
• 2024-12-12 ROS Meetup Singapore
• 2024-12-12 ROS Meetup Barcelona
• 2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline
• 2024-12-16 => 2024-12-19 F1Tenth Sim Racing League at CDC 2024
• 2024-12-18 Aerial Robotics meeting - Xmas with Bitcraze
• 2024-12-22 Open Hardware Summit CFP Deadline
• 2024-12-31 Deadline for Natural Robotics Contest
• 2025-02-01 FOSDEM 25 – See Robotics and Sim Room
• 2025-02-04 => 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh

News

• OSRF Holiday Donation Drive
• November Gazebo Community Meeting: NASA Space ROS Challenge
• Call for Participation: ROS Deliberation Community Group
• Robotic Blending Milestone 5 Highlight Video Live
• Call for euRobotics Technology Transfer Award 2025
• IEEE RAS DEI / Accessibilty Travel Support Grant
• OSRA TGC meeting minutes for October, 2024
• ROS PMC Meeting minutes 2024-12-03
• ROS PMC Meeting minutes 2024-11-26
• ELISA Workshop at NASA Goddard – Space Grade Linux
• How Arduino Forged a Path for Open Hardware - David Cuartielles, Co-Founder, Arduino
• GaussianRPG: 3D Gaussian Rendering PlayGround: an open-source autonomous driving closed-loop simulator demo using 3D Gaussian Splatting tech
• Jeffrey Ichnowski : Learning for Dynamic Robot Manipulation of Deformable Objects
• Sebastian Castro: Research and Industry Future in Robotics
• Weed Dataset (for agriculture)
• Video: Crazyflie at Bitcraze’s Headquarters in Malmö, Sweden
• Teleo raises $16.2M to scale supervised autonomy for heavy equipment
• PickNik Robotics Secures $3 Million in NASA and Space Force
• Amp Robotics raises $91M – The Robot Report
• Clearpath Robotics discusses development of Husky A300 ground vehicle
• ASTM developing testing standards for mobile manipulator
• ARX launches firestick-like platform to make military trucks autonomous
• FOSDEM 2025: Robotics & Simulation… first edition!

ROS

• Gazebo Classic and Citadel End of Life
• New Book - ROS 2 from Scratch
• New Packages for Noetic 2024-12-06
• New packages for Humble Hawksbill 2024-12-05
• New packages for ROS 2 Rolling Ridley 2024-11-26
• Preparing for final Iron Irwini Patch Release and Sync 2024-11-18
• Iron Irwini EOL Plan
• rmw_iceoryx2 v0.1.0 release
• Leveraging ROS build infrastructure for non-ROS packages
• Clearpath Simulator comes to Gazebo Harmonic
• Expose secure communication only with specified entities
• Reference implementation of Zenoh-pico to micro-ROS
• Nav2 Migrated to TwistStamped to replace Twist for cmd_vel Topics
• Towards a ROSdoc integation testing tutorial
• Polar Grid Rviz Plugin - ROS Projects
• FusionSDF: Export Fusion 360 CAD designs to SDF
• ROS 2 Reinforcement learning
• New ROS 2 package for dynamically interpolating 3D LiDAR point clouds
• Help needed: Distribute a ROS package against multiple SDK versions
• ROS 2 Whisper update
• ros-voice-assistant: A ROS 2 package for building voice-enabled robotic applications
• MOANA: Multi-Radar Dataset for Maritime Odometry and Autonomous Navigation Application – MOANA Dataset
• DROID-Splat: End-to-End SLAM with camera calibration, monocular prior integration and dense Rendering
• ROS2-VSC-Toolkit: Visual Studio Code Extension for ROS 2 development
• URDF Visualizer - Visual Studio Plugin
• ros2-tools-to-use-unity-like-gazebo: ros2_control in Unity
• SuperVINS: A real-time visual-inertial SLAM framework for challenging imaging conditions
• Validating the performance of Beluga AMCL
• happypose_ros: ROS 2 wrapper for a 6D pose estimation library
• plainmp: Very fast motion planning for articulated robot, through a bit of premature-optimization (C++ / Python)
• full_coverage_path_planner with a move_base_flex plugin
• VoxelMapPlus_FASTLIO2: FAST-LIO 2 with VoxelMapPlus and STD
• SPTG-LCC: Single-shot, Pixel-level, Target-free and General LiDAR-Camera Extrinsic Self-Calibration
• path_planner: Hybrid A* Path Planner for the KTH Research Concept Vehicle
• InGM-LIO: InGM-LIO: A Multiscale Gaussian Model-Based LiDAR-Inertial Odometry Using Invariant Kalman Filtering.
• 2fast2lamaa: Real-time lidar-inertial odometry and mapping framework for dynamic environments
• kinematic-icp: A LiDAR odometry pipeline for wheeled mobile robots
• python_simple_mppi: Python implementation of MPPI (Model Predictive Path-Integral) controller
• YOLOs-CPP: A high-performance C++ headers for real-time object detection using YOLO models
• ERPoT: Effective and Reliable Pose Tracking for Mobile Robots Based on Lightweight and Compact Polygon Maps
• multicast_parser: ROS Package for parsing multicast data from Motive Tracker 2.0.2 to Appropriate Nodes
• AutoCarROS2: A virtual simulation platform for autonomous vehicle sensing, mapping, control and behaviour methods using ROS 2 and Gazebo.
• SlicerROS2: A Research and Development Module for Image-Guided Robotic Interventions
• unitree-go2-ros2: URDF for Unitree Go2 with Champ Controller
• DPFT: Dual Perspective Fusion Transformer for Camera-Radar-based Object Detection – source
• kidnapped_robot_finder: TROS 2 package for 2d-Lidar scanner based kidnapped robot re-localization

Got a Minute?

We would really appreciate it if you took ten minutes to answer just one ROS question on Robotics Stack Exchange.

1 post - 1 participant

Read full topic

Hi all,

orecham here, one of the committers from the eclipse-iceoryx project.

I’m pleased to announce the alpha release of rmw_iceoryx2, compatible with ROS 2 rolling and available at: GitHub - ekxide/rmw_iceoryx2: ROS 2 RMW implementation for iceoryx2

Why yet another RMW? We have the following goals for rmw_iceoryx2:

1. Bring the high-performance zero-copy shared-memory communication offered by iceoryx2 to ROS 2 applications
2. Provide a unique option for reducing safety certification effort of ROS 2 applications with safety-critical use-cases

Rather than require the entire ROS 2 stack be certified (e.g. for ASIL-D), rmw_iceoryx2 offers an alternative through interoperability between ROS 2 and iceoryx2 applications. This allows the freedom for porting safety-critical components that require certification to iceoryx2 (which is designed for certification) while still participating in the ROS 2 ecosystem.

Current State

With this first alpha release, there is still some work to do and polish to be made. Not all features are yet available and existing ones need thorough real-world validation. Most notably, support for message serialization is not yet available nor service-client communication (waiting on some features to be completed in iceoryx2). Lack of serialization support means that rmw_iceoryx2 can currently only work with self-contained message types, however, this will be one of the first limitations to address next.

Furthermore, only intra-host communication is currently possible. We have plans to introduce host-to-host capabilities in the near future by leveraging existing host-to-host-capable middlewares. Some more info about this is available in the README.

Performance

The current performance_test results are as follow. There is still quite a bit of room for improvement compared to raw iceoryx2:

Contributing and Feedback

We look forward to your feedback! Input from real-world application configurations will be invaluable for bringing rmw_iceoryx2 to stability. Additionally, insights from those experienced with RMW implementations would greatly help improve quality. The current state was achieved using only the information available in the RMW documentation, thus there may be some edge-cases known to veterans which are not properly addressed.

For those who have the capacity to get involved with implementation, we welcome all contributions! We will provide as much support as needed to those who are interested.

Thanks for reading!
Cheers

1 post - 1 participant

Read full topic

We’re happy to announce 2 new packages and 46 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-12-06.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for ROS Noetic

Added Packages [2]:

• ros-noetic-gazebo-noisy-depth-camera: 1.0.1-1
• ros-noetic-hatchbed-common: 0.0.2-1

Updated Packages [46]:

• ros-noetic-ess-imu-driver: 2.0.1-1 → 2.0.2-1
• ros-noetic-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-messages: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-noetic-foxglove-bridge: 0.7.10-1 → 0.8.1-1
• ros-noetic-inorbit-republisher: 0.3.0-1 → 0.3.2-1
• ros-noetic-nodelet: 1.11.0-2 → 1.11.1-1
• ros-noetic-nodelet-core: 1.11.0-2 → 1.11.1-1
• ros-noetic-nodelet-topic-tools: 1.11.0-2 → 1.11.1-1
• ros-noetic-rc-reason-clients: 0.3.1-1 → 0.4.0-2
• ros-noetic-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
• ros-noetic-rtabmap: 0.21.6-1 → 0.21.9-1
• ros-noetic-rtabmap-conversions: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-costmap-plugins: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-demos: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-examples: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-launch: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-legacy: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-msgs: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-odom: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-python: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-ros: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-rviz-plugins: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-slam: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-sync: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-util: 0.21.5-1 → 0.21.9-1
• ros-noetic-rtabmap-viz: 0.21.5-1 → 0.21.9-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

• Felix Ruess
• Geoffrey Biggs
• Hans-Joachim Krauch
• InOrbit
• Jean-Pierre Busch
• Marc Alban
• Martin Pecka
• Mathieu Labbe
• Raymond Chow

2 posts - 2 participants

Read full topic

Due to a one-time scheduling conflict, the Open-RMF Project Management Committee session that is normally scheduled for 2024-12-17T01:00:00Z UTC will instead take place one hour later at 2024-12-17T02:00:00Z UTC. This change is reflected in the official OSRF events calendar.

Sessions will return to the normal time afterwards.

1 post - 1 participant

Read full topic

We’re happy to announce a new Humble release!

This sync brings several new packages and some updates to ROS 2 core packages. (I haven’t included the project board for patch info because there was nothing on it.)

Package Updates for Humble

Added Packages [34]:

• ros-humble-adi-3dtof-image-stitching: 2.1.0-1
• ros-humble-adi-3dtof-image-stitching-dbgsym: 2.1.0-1
• ros-humble-axis-camera: 2.0.3-1
• ros-humble-axis-description: 2.0.3-1
• ros-humble-axis-msgs: 2.0.3-1
• ros-humble-axis-msgs-dbgsym: 2.0.3-1
• ros-humble-camera-info-manager-py: 3.1.10-1
• ros-humble-clearpath-motor-msgs: 1.0.1-1
• ros-humble-clearpath-motor-msgs-dbgsym: 1.0.1-1
• ros-humble-clearpath-ros2-socketcan-interface: 1.0.0-1
• ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.0-1
• ros-humble-dual-laser-merger: 0.1.1-1
• ros-humble-dual-laser-merger-dbgsym: 0.1.1-1
• ros-humble-hatchbed-common: 0.1.1-1
• ros-humble-hri-face-body-matcher: 2.1.0-1
• ros-humble-hri-face-body-matcher-dbgsym: 2.1.0-1
• ros-humble-hri-privacy-msgs: 1.2.0-1
• ros-humble-hri-privacy-msgs-dbgsym: 1.2.0-1
• ros-humble-jacro: 0.2.0-1
• ros-humble-laser-segmentation: 3.0.2-1
• ros-humble-laser-segmentation-dbgsym: 3.0.2-1
• ros-humble-log-view: 0.2.5-1
• ros-humble-log-view-dbgsym: 0.2.5-1
• ros-humble-pose-broadcaster: 2.38.0-1
• ros-humble-pose-broadcaster-dbgsym: 2.38.0-1
• ros-humble-ptz-action-server-msgs: 2.0.3-1
• ros-humble-ptz-action-server-msgs-dbgsym: 2.0.3-1
• ros-humble-rosbag2-to-video: 1.0.1-1
• ros-humble-simple-grasping: 0.5.0-1
• ros-humble-simple-grasping-dbgsym: 0.5.0-1
• ros-humble-slg-msgs: 3.9.1-1
• ros-humble-slg-msgs-dbgsym: 3.9.1-1
• ros-humble-zed-msgs: 4.2.2-1
• ros-humble-zed-msgs-dbgsym: 4.2.2-1

Updated Packages [580]:

• ros-humble-ackermann-steering-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-ackermann-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-adi-tmcl: 2.0.0-1 → 2.0.3-2
• ros-humble-adi-tmcl-dbgsym: 2.0.0-1 → 2.0.3-2
• ros-humble-admittance-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-admittance-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-ament-cmake: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-auto: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-core: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-definitions: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-dependencies: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-include-directories: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-interfaces: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-libraries: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-link-flags: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-export-targets: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-gen-version-h: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-gmock: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-google-benchmark: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-gtest: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-include-directories: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-libraries: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-nose: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-pytest: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-python: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-target-dependencies: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-test: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-vendor-package: 1.3.10-1 → 1.3.11-1
• ros-humble-ament-cmake-version: 1.3.10-1 → 1.3.11-1
• ros-humble-autoware-lanelet2-extension: 0.6.0-1 → 0.6.2-1
• ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.0-1 → 0.6.2-1
• ros-humble-autoware-lanelet2-extension-python: 0.6.0-1 → 0.6.2-1
• ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.0-1 → 0.6.2-1
• ros-humble-backward-ros: 1.0.5-1 → 1.0.6-1
• ros-humble-backward-ros-dbgsym: 1.0.5-1 → 1.0.6-1
• ros-humble-bicycle-steering-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-bicycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-bosch-locator-bridge: 2.1.11-1 → 2.1.13-1
• ros-humble-bosch-locator-bridge-dbgsym: 2.1.11-1 → 2.1.13-1
• ros-humble-bosch-locator-bridge-utils: 2.1.11-1 → 2.1.13-1
• ros-humble-bosch-locator-bridge-utils-dbgsym: 2.1.11-1 → 2.1.13-1
• ros-humble-camera-calibration-parsers: 3.1.9-1 → 3.1.10-1
• ros-humble-camera-calibration-parsers-dbgsym: 3.1.9-1 → 3.1.10-1
• ros-humble-camera-info-manager: 3.1.9-1 → 3.1.10-1
• ros-humble-camera-info-manager-dbgsym: 3.1.9-1 → 3.1.10-1
• ros-humble-camera-ros: 0.1.0-2 → 0.2.0-1
• ros-humble-camera-ros-dbgsym: 0.1.0-2 → 0.2.0-1
• ros-humble-chomp-motion-planner: 2.5.5-1 → 2.5.6-1
• ros-humble-chomp-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-clearpath-common: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-config: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-config-live: 0.3.0-1 → 1.0.0-1
• ros-humble-clearpath-control: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-customization: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-description: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-desktop: 0.3.0-1 → 1.0.0-1
• ros-humble-clearpath-generator-common: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-generator-common-dbgsym: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-generator-gz: 0.3.0-1 → 1.0.0-1
• ros-humble-clearpath-gz: 0.3.0-1 → 1.0.0-1
• ros-humble-clearpath-manipulators: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-manipulators-description: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-mounts-description: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-msgs: 1.0.0-1 → 1.0.1-1
• ros-humble-clearpath-nav2-demos: 0.2.0-1 → 1.0.0-1
• ros-humble-clearpath-platform-description: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-platform-msgs: 1.0.0-1 → 1.0.1-1
• ros-humble-clearpath-platform-msgs-dbgsym: 1.0.0-1 → 1.0.1-1
• ros-humble-clearpath-sensors-description: 0.3.4-1 → 1.0.0-1
• ros-humble-clearpath-simulator: 0.3.0-1 → 1.0.0-1
• ros-humble-clearpath-viz: 0.3.0-1 → 1.0.0-1
• ros-humble-control-msgs: 4.6.0-1 → 4.7.0-1
• ros-humble-control-msgs-dbgsym: 4.6.0-1 → 4.7.0-1
• ros-humble-controller-interface: 2.43.1-1 → 2.44.0-1
• ros-humble-controller-interface-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-controller-manager: 2.43.1-1 → 2.44.0-1
• ros-humble-controller-manager-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-controller-manager-msgs: 2.43.1-1 → 2.44.0-1
• ros-humble-controller-manager-msgs-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-costmap-queue: 1.1.16-1 → 1.1.17-1
• ros-humble-costmap-queue-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-cyclonedds: 0.10.4-1 → 0.10.5-2
• ros-humble-cyclonedds-dbgsym: 0.10.4-1 → 0.10.5-2
• ros-humble-depthai-bridge: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-bridge-dbgsym: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-descriptions: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-examples: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-examples-dbgsym: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-filters: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-filters-dbgsym: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-ros: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-ros-driver: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-ros-driver-dbgsym: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-ros-msgs: 2.10.3-1 → 2.10.4-1
• ros-humble-depthai-ros-msgs-dbgsym: 2.10.3-1 → 2.10.4-1
• ros-humble-diff-drive-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-diff-drive-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-dwb-core: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-core-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-critics: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-critics-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-msgs: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-plugins: 1.1.16-1 → 1.1.17-1
• ros-humble-dwb-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-effort-controllers: 2.37.3-1 → 2.38.0-1
• ros-humble-effort-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-etsi-its-cam-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-coding-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-conversion-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cpm-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cpm-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cpm-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-denm-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-denm-coding-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-denm-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-denm-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-denm-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-messages: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-msgs-utils: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-primitives-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-rviz-plugins: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-rviz-plugins-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-vam-ts-coding: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1 → 2.4.0-1
• ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1 → 2.4.0-1
• ros-humble-examples-rclcpp-async-client: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-async-client-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-cbg-executor: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-cbg-executor-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-action-client: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-action-client-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-action-server: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-action-server-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-client: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-client-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-composition: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-composition-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-publisher: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-publisher-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-service: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-service-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-subscriber: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-subscriber-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-timer: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-minimal-timer-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-multithreaded-executor: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-multithreaded-executor-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-wait-set: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclcpp-wait-set-dbgsym: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-executors: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-guard-conditions: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-action-client: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-action-server: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-client: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-publisher: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-service: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-minimal-subscriber: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-rclpy-pointcloud-publisher: 0.15.2-1 → 0.15.3-1
• ros-humble-examples-tf2-py: 0.25.8-1 → 0.25.9-1
• ros-humble-fastrtps: 2.6.8-1 → 2.6.9-1
• ros-humble-fastrtps-dbgsym: 2.6.8-1 → 2.6.9-1
• ros-humble-flir-camera-description: 2.1.17-1 → 3.0.0-1
• ros-humble-flir-camera-msgs: 2.1.17-1 → 3.0.0-1
• ros-humble-flir-camera-msgs-dbgsym: 2.1.17-1 → 3.0.0-1
• ros-humble-force-torque-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
• ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-forward-command-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-forward-command-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-foxglove-bridge: 0.8.0-1 → 0.8.1-1
• ros-humble-foxglove-bridge-dbgsym: 0.8.0-1 → 0.8.1-1
• ros-humble-foxglove-compressed-video-transport: 1.0.0-1 → 1.0.1-1
• ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.0-1 → 1.0.1-1
• ros-humble-geometry2: 0.25.8-1 → 0.25.9-1
• ros-humble-gripper-controllers: 2.37.3-1 → 2.38.0-1
• ros-humble-gripper-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-hardware-interface: 2.43.1-1 → 2.44.0-1
• ros-humble-hardware-interface-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-hardware-interface-testing: 2.43.1-1 → 2.44.0-1
• ros-humble-hardware-interface-testing-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-image-common: 3.1.9-1 → 3.1.10-1
• ros-humble-image-transport: 3.1.9-1 → 3.1.10-1
• ros-humble-image-transport-dbgsym: 3.1.9-1 → 3.1.10-1
• ros-humble-imu-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
• ros-humble-imu-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-interactive-marker-twist-server: 2.1.0-2 → 2.1.1-1
• ros-humble-interactive-marker-twist-server-dbgsym: 2.1.0-2 → 2.1.1-1
• ros-humble-joint-limits: 2.43.1-1 → 2.44.0-1
• ros-humble-joint-limits-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-joint-state-broadcaster: 2.37.3-1 → 2.38.0-1
• ros-humble-joint-state-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-joint-trajectory-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-joy-teleop: 1.6.0-1 → 1.7.0-1
• ros-humble-key-teleop: 1.6.0-1 → 1.7.0-1
• ros-humble-launch: 1.0.6-1 → 1.0.7-1
• ros-humble-launch-pytest: 1.0.6-1 → 1.0.7-1
• ros-humble-launch-ros: 0.19.7-2 → 0.19.8-1
• ros-humble-launch-testing: 1.0.6-1 → 1.0.7-1
• ros-humble-launch-testing-ament-cmake: 1.0.6-1 → 1.0.7-1
• ros-humble-launch-testing-examples: 0.15.2-1 → 0.15.3-1
• ros-humble-launch-testing-ros: 0.19.7-2 → 0.19.8-1
• ros-humble-launch-xml: 1.0.6-1 → 1.0.7-1
• ros-humble-launch-yaml: 1.0.6-1 → 1.0.7-1
• ros-humble-leo: 1.2.3-1 → 1.2.4-1
• ros-humble-leo-bringup: 1.4.0-1 → 1.5.0-1
• ros-humble-leo-description: 1.2.3-1 → 1.2.4-1
• ros-humble-leo-fw: 1.4.0-1 → 1.5.0-1
• ros-humble-leo-fw-dbgsym: 1.4.0-1 → 1.5.0-1
• ros-humble-leo-gz-bringup: 1.1.0-1 → 1.1.1-1
• ros-humble-leo-gz-plugins: 1.1.0-1 → 1.1.1-1
• ros-humble-leo-gz-plugins-dbgsym: 1.1.0-1 → 1.1.1-1
• ros-humble-leo-gz-worlds: 1.1.0-1 → 1.1.1-1
• ros-humble-leo-msgs: 1.2.3-1 → 1.2.4-1
• ros-humble-leo-msgs-dbgsym: 1.2.3-1 → 1.2.4-1
• ros-humble-leo-robot: 1.4.0-1 → 1.5.0-1
• ros-humble-leo-simulator: 1.1.0-1 → 1.1.1-1
• ros-humble-leo-teleop: 1.2.3-1 → 1.2.4-1
• ros-humble-libstatistics-collector: 1.3.2-1 → 1.3.4-1
• ros-humble-libstatistics-collector-dbgsym: 1.3.2-1 → 1.3.4-1
• ros-humble-mcap-vendor: 0.15.12-1 → 0.15.13-1
• ros-humble-mcap-vendor-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-microstrain-inertial-description: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-driver: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-driver-dbgsym: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-examples: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-msgs: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-msgs-dbgsym: 4.4.0-1 → 4.5.0-1
• ros-humble-microstrain-inertial-rqt: 4.4.0-1 → 4.5.0-1
• ros-humble-mouse-teleop: 1.6.0-1 → 1.7.0-1
• ros-humble-moveit: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-chomp-optimizer-adapter: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-common: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-configs-utils: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-core: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-core-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-hybrid-planning: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-hybrid-planning-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-kinematics: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-kinematics-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-planners: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-planners-chomp: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-planners-chomp-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-planners-ompl: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-planners-ompl-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-plugins: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-resources-prbt-moveit-config: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-resources-prbt-pg70-support: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-resources-prbt-support: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-benchmarks: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-control-interface: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-control-interface-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-move-group: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-move-group-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-occupancy-map-monitor: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-perception: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-perception-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-planning: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-planning-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-planning-interface: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-robot-interaction: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-visualization: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-visualization-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-warehouse: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-ros-warehouse-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-runtime: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-servo: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-servo-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-app-plugins: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-assistant: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-assistant-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-controllers: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-controllers-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-core-plugins: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-framework: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-framework-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-srdf-plugins: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-simple-controller-manager: 2.5.5-1 → 2.5.6-1
• ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-mp2p-icp: 1.6.2-1 → 1.6.3-1
• ros-humble-mp2p-icp-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-humble-mrpt-apps: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-apps-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libapps: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libapps-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libbase: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libbase-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libgui: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libgui-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libhwdrivers: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libmaps: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libmaps-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libmath: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libmath-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libnav: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libnav-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libobs: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libobs-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libopengl: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libopengl-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libposes: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libposes-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libros-bridge: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libros-bridge-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libslam: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libslam-dbgsym: 2.14.4-1 → 2.14.5-1
• ros-humble-mrpt-libtclap: 2.14.4-1 → 2.14.5-1
• ros-humble-nav-2d-msgs: 1.1.16-1 → 1.1.17-1
• ros-humble-nav-2d-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav-2d-utils: 1.1.16-1 → 1.1.17-1
• ros-humble-nav-2d-utils-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-amcl: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-amcl-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-behavior-tree: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-behavior-tree-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-behaviors: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-behaviors-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-bringup: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-bt-navigator: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-bt-navigator-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-collision-monitor: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-collision-monitor-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-common: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-constrained-smoother: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-constrained-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-controller-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-core: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-costmap-2d: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-costmap-2d-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-dwb-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-graceful-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-graceful-controller-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-lifecycle-manager: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-map-server: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-map-server-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-mppi-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-mppi-controller-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-msgs: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-msgs-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-navfn-planner: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-navfn-planner-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-planner: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-planner-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-rotation-shim-controller: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-rviz-plugins: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-rviz-plugins-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-simple-commander: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-smac-planner: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-smac-planner-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-smoother: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-system-tests: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-system-tests-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-theta-star-planner: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-theta-star-planner-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-util: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-util-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-velocity-smoother: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-velocity-smoother-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-voxel-grid: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-voxel-grid-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-waypoint-follower: 1.1.16-1 → 1.1.17-1
• ros-humble-nav2-waypoint-follower-dbgsym: 1.1.16-1 → 1.1.17-1
• ros-humble-navigation2: 1.1.16-1 → 1.1.17-1
• ros-humble-novatel-gps-driver: 4.1.3-1 → 4.2.0-1
• ros-humble-novatel-gps-driver-dbgsym: 4.1.3-1 → 4.2.0-1
• ros-humble-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1
• ros-humble-novatel-gps-msgs-dbgsym: 4.1.3-1 → 4.2.0-1
• ros-humble-octomap-msgs: 2.0.0-3 → 2.0.1-1
• ros-humble-octomap-msgs-dbgsym: 2.0.0-3 → 2.0.1-1
• ros-humble-odom-to-tf-ros2: 1.0.2-1 → 1.0.4-1
• ros-humble-odom-to-tf-ros2-dbgsym: 1.0.2-1 → 1.0.4-1
• ros-humble-openni2-camera: 2.0.2-1 → 2.0.3-1
• ros-humble-openni2-camera-dbgsym: 2.0.2-1 → 2.0.3-1
• ros-humble-osrf-pycommon: 2.0.2-2 → 2.1.4-1
• ros-humble-pal-gripper: 3.3.0-1 → 3.4.0-1
• ros-humble-pal-gripper-controller-configuration: 3.3.0-1 → 3.4.0-1
• ros-humble-pal-gripper-description: 3.3.0-1 → 3.4.0-1
• ros-humble-pal-gripper-simulation: 3.3.0-1 → 3.4.0-1
• ros-humble-pal-maps: 0.0.4-1 → 0.0.5-1
• ros-humble-pal-statistics: 2.3.1-1 → 2.5.0-1
• ros-humble-pal-statistics-dbgsym: 2.3.1-1 → 2.5.0-1
• ros-humble-pal-statistics-msgs: 2.3.1-1 → 2.5.0-1
• ros-humble-pal-statistics-msgs-dbgsym: 2.3.1-1 → 2.5.0-1
• ros-humble-pid-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-pid-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-pilz-industrial-motion-planner: 2.5.5-1 → 2.5.6-1
• ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-pilz-industrial-motion-planner-testutils: 2.5.5-1 → 2.5.6-1
• ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.5-1 → 2.5.6-1
• ros-humble-pmb2-2dnav: 4.2.0-1 → 4.5.0-1
• ros-humble-pmb2-bringup: 5.3.1-1 → 5.4.0-1
• ros-humble-pmb2-controller-configuration: 5.3.1-1 → 5.4.0-1
• ros-humble-pmb2-description: 5.3.1-1 → 5.4.0-1
• ros-humble-pmb2-gazebo: 4.0.16-1 → 4.1.0-1
• ros-humble-pmb2-laser-sensors: 4.2.0-1 → 4.5.0-1
• ros-humble-pmb2-navigation: 4.2.0-1 → 4.5.0-1
• ros-humble-pmb2-robot: 5.3.1-1 → 5.4.0-1
• ros-humble-pmb2-simulation: 4.0.16-1 → 4.1.0-1
• ros-humble-position-controllers: 2.37.3-1 → 2.38.0-1
• ros-humble-position-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-python-mrpt: 2.14.4-1 → 2.14.5-1
• ros-humble-range-sensor-broadcaster: 2.37.3-1 → 2.38.0-1
• ros-humble-range-sensor-broadcaster-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-rc-reason-clients: 0.3.1-1 → 0.4.0-2
• ros-humble-rc-reason-msgs: 0.3.1-1 → 0.4.0-2
• ros-humble-rc-reason-msgs-dbgsym: 0.3.1-1 → 0.4.0-2
• ros-humble-rclcpp: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-action: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-action-dbgsym: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-components: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-components-dbgsym: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-dbgsym: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-lifecycle: 16.0.10-1 → 16.0.11-1
• ros-humble-rclcpp-lifecycle-dbgsym: 16.0.10-1 → 16.0.11-1
• ros-humble-rclpy: 3.3.14-1 → 3.3.15-1
• ros-humble-rcpputils: 2.4.3-1 → 2.4.4-1
• ros-humble-rcpputils-dbgsym: 2.4.3-1 → 2.4.4-1
• ros-humble-realtime-tools: 2.7.0-1 → 2.8.1-1
• ros-humble-realtime-tools-dbgsym: 2.7.0-1 → 2.8.1-1
• ros-humble-rmf-building-map-tools: 1.6.2-1 → 1.6.3-1
• ros-humble-rmf-traffic-editor: 1.6.2-1 → 1.6.3-1
• ros-humble-rmf-traffic-editor-assets: 1.6.2-1 → 1.6.3-1
• ros-humble-rmf-traffic-editor-dbgsym: 1.6.2-1 → 1.6.3-1
• ros-humble-rmf-traffic-editor-test-maps: 1.6.2-1 → 1.6.3-1
• ros-humble-rmw-connextdds: 0.11.2-1 → 0.11.3-1
• ros-humble-rmw-connextdds-common: 0.11.2-1 → 0.11.3-1
• ros-humble-rmw-connextdds-common-dbgsym: 0.11.2-1 → 0.11.3-1
• ros-humble-rmw-connextdds-dbgsym: 0.11.2-1 → 0.11.3-1
• ros-humble-robot-calibration: 0.8.1-1 → 0.8.2-1
• ros-humble-robot-calibration-dbgsym: 0.8.1-1 → 0.8.2-1
• ros-humble-robot-calibration-msgs: 0.8.1-1 → 0.8.2-1
• ros-humble-robot-calibration-msgs-dbgsym: 0.8.1-1 → 0.8.2-1
• ros-humble-ros2-control: 2.43.1-1 → 2.44.0-1
• ros-humble-ros2-control-test-assets: 2.43.1-1 → 2.44.0-1
• ros-humble-ros2-controllers: 2.37.3-1 → 2.38.0-1
• ros-humble-ros2-controllers-test-nodes: 2.37.3-1 → 2.38.0-1
• ros-humble-ros2bag: 0.15.12-1 → 0.15.13-1
• ros-humble-ros2controlcli: 2.43.1-1 → 2.44.0-1
• ros-humble-ros2launch: 0.19.7-2 → 0.19.8-1
• ros-humble-rosbag2: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-compression: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-compression-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-compression-zstd: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-compression-zstd-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-cpp: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-cpp-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-interfaces: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-interfaces-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-performance-benchmarking: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-py: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-default-plugins: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-default-plugins-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-mcap: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-mcap-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-mcap-testdata: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-storage-mcap-testdata-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-test-common: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-tests: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-transport: 0.15.12-1 → 0.15.13-1
• ros-humble-rosbag2-transport-dbgsym: 0.15.12-1 → 0.15.13-1
• ros-humble-rosidl-adapter: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-cli: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-cmake: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-generator-c: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-generator-cpp: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-parser: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-runtime-c: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-runtime-c-dbgsym: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-runtime-cpp: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-typesupport-c: 2.0.1-1 → 2.0.2-1
• ros-humble-rosidl-typesupport-c-dbgsym: 2.0.1-1 → 2.0.2-1
• ros-humble-rosidl-typesupport-cpp: 2.0.1-1 → 2.0.2-1
• ros-humble-rosidl-typesupport-cpp-dbgsym: 2.0.1-1 → 2.0.2-1
• ros-humble-rosidl-typesupport-interface: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-typesupport-introspection-c: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-typesupport-introspection-c-dbgsym: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-typesupport-introspection-cpp: 3.1.5-2 → 3.1.6-1
• ros-humble-rosidl-typesupport-introspection-cpp-dbgsym: 3.1.5-2 → 3.1.6-1
• ros-humble-rqt-controller-manager: 2.43.1-1 → 2.44.0-1
• ros-humble-rqt-joint-trajectory-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-rti-connext-dds-cmake-module: 0.11.2-1 → 0.11.3-1
• ros-humble-rviz-assimp-vendor: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-common: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-common-dbgsym: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-default-plugins: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-default-plugins-dbgsym: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-ogre-vendor: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-ogre-vendor-dbgsym: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-rendering: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-rendering-dbgsym: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-rendering-tests: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz-visual-testing-framework: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz2: 11.2.13-1 → 11.2.14-1
• ros-humble-rviz2-dbgsym: 11.2.13-1 → 11.2.14-1
• ros-humble-shared-queues-vendor: 0.15.12-1 → 0.15.13-1
• ros-humble-spinnaker-camera-driver: 2.1.17-1 → 3.0.0-1
• ros-humble-spinnaker-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
• ros-humble-spinnaker-synchronized-camera-driver: 2.1.17-1 → 3.0.0-1
• ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 2.1.17-1 → 3.0.0-1
• ros-humble-sqlite3-vendor: 0.15.12-1 → 0.15.13-1
• ros-humble-steering-controllers-library: 2.37.3-1 → 2.38.0-1
• ros-humble-steering-controllers-library-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-teleop-tools: 1.6.0-1 → 1.7.0-1
• ros-humble-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1
• ros-humble-teleop-tools-msgs-dbgsym: 1.6.0-1 → 1.7.0-1
• ros-humble-tf2: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-bullet: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-dbgsym: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-eigen: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-eigen-kdl: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-eigen-kdl-dbgsym: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-geometry-msgs: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-kdl: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-msgs: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-msgs-dbgsym: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-py: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-py-dbgsym: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-ros: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-ros-dbgsym: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-ros-py: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-sensor-msgs: 0.25.8-1 → 0.25.9-1
• ros-humble-tf2-tools: 0.25.8-1 → 0.25.9-1
• ros-humble-tiago-2dnav: 4.2.0-1 → 4.5.0-1
• ros-humble-tiago-bringup: 4.6.0-1 → 4.7.1-1
• ros-humble-tiago-controller-configuration: 4.6.0-1 → 4.7.1-1
• ros-humble-tiago-description: 4.6.0-1 → 4.7.1-1
• ros-humble-tiago-gazebo: 4.2.0-1 → 4.3.0-1
• ros-humble-tiago-gazebo-dbgsym: 4.2.0-1 → 4.3.0-1
• ros-humble-tiago-laser-sensors: 4.2.0-1 → 4.5.0-1
• ros-humble-tiago-moveit-config: 3.1.0-1 → 3.1.1-1
• ros-humble-tiago-navigation: 4.2.0-1 → 4.5.0-1
• ros-humble-tiago-robot: 4.6.0-1 → 4.7.1-1
• ros-humble-tiago-simulation: 4.2.0-1 → 4.3.0-1
• ros-humble-transmission-interface: 2.43.1-1 → 2.44.0-1
• ros-humble-transmission-interface-dbgsym: 2.43.1-1 → 2.44.0-1
• ros-humble-tricycle-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-tricycle-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-tricycle-steering-controller: 2.37.3-1 → 2.38.0-1
• ros-humble-tricycle-steering-controller-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-twist-stamper: 0.0.3-1 → 0.0.5-1
• ros-humble-ur-client-library: 1.4.0-1 → 1.5.0-1
• ros-humble-ur-client-library-dbgsym: 1.4.0-1 → 1.5.0-1
• ros-humble-velocity-controllers: 2.37.3-1 → 2.38.0-1
• ros-humble-velocity-controllers-dbgsym: 2.37.3-1 → 2.38.0-1
• ros-humble-zstd-vendor: 0.15.12-1 → 0.15.13-1

Removed Packages [6]:

• ros-humble-clearpath-platform
• ros-humble-clearpath-platform-dbgsym
• ros-humble-mrpt2
• ros-humble-mrpt2-dbgsym
• ros-humble-omni-base-maps
• ros-humble-swri-prefix-tools

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

• Adam Serafin
• Aditya Pande
• Aina Irisarri
• Alberto Tudela
• Alejandro Hernandez Cordero
• Alexander Gutenkunst
• Alexey Merzlyakov
• Analog Devices
• Andrea Sorbini
• Antonio Brandi
• Bence Magyar
• Bernd Pfrommer
• Blake Anderson
• Brandon Ong
• Brian Wilcox
• Błażej Sowa
• Carl Delsey
• Carlos Orduno
• Chittaranjan Srinivas Swaminathan
• Chris Iverach-Brereton
• Chris Lalancette
• Christian Henkel
• Christian Rauch
• David V. Lu!!
• Denis Štogl
• Eclipse Foundation, Inc.
• Enrique Fernandez
• Evan Flynn
• Felix Exner
• Felix Ruess
• Fictionlab
• Foxglove
• George Stavrinos
• Hans-Joachim Krauch
• Henning Kayser
• Ivan Paunovic
• Jacob Perron
• Jafar Uruc
• Jean-Pierre Busch
• Jordan Palacios
• Jordi Pages
• Jose Mastrangelo
• Jose-Luis Blanco-Claraco
• Josh Newans
• Luis Camero
• Luka Juricic
• Mamoru Sobue
• Marc Alban
• Matej Vargovcik
• Michael Ferguson
• Michael Görner
• Michael Jeronimo
• Michael Orlov
• Michel Hidalgo
• Miguel Company
• Mike Purvis
• Mohammad Haghighipanah
• Morgan Quigley
• MoveIt Release Team
• P. J. Reed
• ROS Tooling Working Group
• Raghavender Sahdev
• Ralph Lange
• Rob Fisher
• Robert Wilbrandt
• Roni Kreinin
• STEREOLABS
• Shane Loretz
• Stefan Laible
• Steve Macenski
• Séverin Lemaignan
• TIAGo PAL support team
• TIAGo support team
• Tony Baltovski
• Victor López
• William Woodall
• Wolfgang Merkt
• mitsudome-r
• pradyum
• ruess
• steve

1 post - 1 participant

Read full topic

Hello everyone,

I have successfully ported Clearpath Robotics’s open-source simulator clearpath_simulator into Gazebo Harmonic LTS.

Key changes include adding support for Xbox One controllers, support for custom robot.yaml names and automatic Twist message conversion to TwistStamped required by the newer builds of ros2_controllers and Gazebo. The simulator has been tested to work in Ubuntu 22.04 (source build). Presently, only A200 Husky is supported. Version 0.2 will add RGB-D sensor and build testing in Ubuntu 24.04.

To accommodate a number of changes made to almost all the original dependent packages, I have opted to host my derived work separately here: GitHub - Mechazo11/clearpath_simulator_harmonic: A port of Clearpath Simulator, compatible with ROS 2 Jazzy and Gazebo Harmonic

A big shout-out to Clearpath Robotics team for making the original simulator publicly available. I hope this work proves valuable to the community. If you have any questions, concerns or would like to contribute please don’t hesitate to reaching out to me.

With best regards,
Azmyin Md. Kamal

1 post - 1 participant

Read full topic

Hi ROS developers,

Asking thoughts and ideas!

I think this is more like discussion to explore than a question, I would like to have feedback from the community how to handle this situation to support 3rd party device.

Original issue: Expose secure communication only with specified entities. · Issue #326 · ros2/sros2 · GitHub

• For performance consideration, it would be better to keep the localhost communication in robot without secured authentication nor encryption. (basically it uses localhost in robot system, but some specific nodes to be exposed.)

I am trying to find out what could be best solution to support above requirement with secured communication with sros2.

If you have any experience, please enlighten me

Regards,
Tomoya

6 posts - 3 participants

Read full topic

Hi,
The next meeting of the Client Library Working Group will be this Friday, 6th December 2024 at 8 AM Pacific Time.

• Meeting link: https://meet.google.com/oij-atzj-znw
• Calendar invite: https://calendar.app.google/WDSVtbpSu5SrNc1Q8
• Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg

We will be reviewing the charter proposal for the ROS 2 Client Library Working Group and continue the discussions from the previous meetings.

2 posts - 1 participant

Read full topic

Hello all,

After our successful workshop at ROSCon 2024, the ROS Deliberation Community Group is resuming its focus on monthly meetings to engage with the community.

For those who were formerly attending the meetings before we spent time preparing for the workshop, the time is right to start attending again! If you are considering attending for the first time, or have never heard of this Community Group before, we look forward to seeing you as well.

Either way, we’d like to hear from you all about possible topics for subsequent meetings in the new year. Some initial ideas:

• Putting together a survey document of ROS 2 Deliberation Technologies, very much inspired by the great Nav2 paper.
• Collaborating on the development of open-source software tools, or examples using those tools, for robot deliberation.
• Presentations from people interested in sharing their work (though we’d like to also have time for working discussions as well).

If anyone wants to share ideas or ask any questions, feel free to post here, or just show up to the next meeting(s)! You can find more information, including how to sign up in this document.

3 posts - 2 participants

Read full topic

Original Post

Hi Everyone,

This is your friendly reminder that as outlined here Gazebo Classic (i.e. Gazebo 11) will officially go end of life on Friday, January 31st, 2025. Gazebo Citadel, our first modern Gazebo LTS release, will go end of life on December 30th, 2024. Gazebo Classic users are advised to transition to an LTS modern Gazebo release as soon as possible (we recommend Gazebo Harmonic, or Gazebo Fortress). We recommend that Gazebo Citadel users also upgrade to either Harmonic or Fortress. Information about currently supported Gazebo versions and support windows, can be found here.

What does End of Life Mean?

Users often ask us, “what does end of life mean?” To put it briefly, end of life means that the Gazebo team will no longer support that particular Gazebo release. In practical terms, this means that we will no longer be providing the following for Gazebo Classic:

• New features or capabilities
• Security updates
• Bug fixes, patches or support
• Updated binaries

It is also worth noting the things that won’t change after Gazebo Classic goes end of life:

• Gazebo Classic binaries will not suddenly disappear
• Users will not need to migrate immediately, but they should migrate as soon as possible
• Your project will not suddenly stop working on January 31st

Why do we End of Life Gazebo releases?

We End of Life particular Gazebo releases for the same reason that most people don’t use Windows XP or an iPhone 4 anymore: better versions of the software are now available and we simply don’t have the resources to support every Gazebo release into perpetuity. Marking a particular version of Gazebo end of life frees up resources to help support newer and better versions of the software. More to the point, the underlying packages and operating system (Ubuntu Focal) used by Gazebo Classic also goes end of life in April 2025.

How do I upgrade to a newer version of Gazebo and which one should I use?

We recommend that Gazebo Classic users upgrade to the latest long term support release of modern Gazebo, Gazebo Harmonic. Gazebo Harmonic works best on Ubuntu Jammy (22.04) and Ubuntu Noble (24.04) and will be supported until September of 2028. Gazebo Classic users who still use ROS 1 will also need to upgrade to ROS 2 Jazzy to use Gazebo Harmonic. It is worth noting that all of ROS 1, including ROS 1 Noetic, will go end of life on May 23rd, 2025. Our internal estimates indicate that over 80% of the ROS community has already upgraded to ROS 2, and 67% of Gazebo users have already upgraded to modern Gazebo.

The modern Gazebo documentation includes a variety of guides and tutorials on how to migrate your project from Gazebo Classic to modern Gazebo. Similarly, the ROS 2 documentation provides step by step instructions on how to migrate your ROS 1 project to ROS 2. If you get stuck during migration, we would encourage you to use the Open Robotics Discord, the Gazebo Sim Community, and Robotics Stack Exchange to find help.

Help Spread the Word

We realize that many Gazebo Classic users don’t really track Gazebo end of life dates, or regularly visit Gazebosim Community, that’s why we’ve decided to include some notifications about Gazebo Classic’s impending end of life in our latest Gazebo Classic update. Starting this week, after updating Gazebo Classic users will be notified via debug output and pop-ups of the upcoming end of life date. These warnings can be suppressed by simply setting a “GAZEBO_SUPPRESS_EOL_WARNING” environment variable.

We would appreciate the community’s help in spreading the word about the upcoming Gazebo Classic End of Life. If you work on a team that is still using Gazebo Classic please take a moment in the next week or two to discuss upgrade paths with your team and the importance of upgrading as soon as possible.

2 posts - 1 participant

Read full topic

I’ve posted a poll on the Moveit 2 discussions board asking for feedback regarding which versions people are using, as it seems like it’d be interesting to gather some quantitative data.

Figured I’d post it here, too, for more visibility:

1 post - 1 participant

Read full topic

Community Page

Meeting Link

Calendar Link

2024-12-05T15:00:00Z UTC

This month our friends from Reply will be presenting on work that they’ve been doing on robotics system integration using Open-RMF.

2 posts - 2 participants

Read full topic

Hey guys, I just migrated from ROS1 to ROS2 and I am running ROS2 Humble Hawksbill with Gazebo Harmonic (ik it’s not the default installation but yeah I pulled Harmonic separately). I am working on a basic project to bring a robot present in my academia to gazebo and I noticed that there is close to no documentation about the list of sensors and how to use them in our xacro files. There is some basic introduction here. But I don’t see any list of sensors and how to use them anywhere. Does this call for creating a well-defined documentation or am I really missing any website?

13 posts - 9 participants

Read full topic

Hi Everyone,

Just a quick note before everyone heads off for the long holiday weekend here in the States. Next Tuesday is Giving Tuesday in the US, a day when many people make their big charitable donations for the holiday season.

This year, we’ve set up a donations page for the Open Source Robotics Foundation (OSRF) where you can specifically designate how you’d like your donation to be used. Want to help fund our infrastructure costs? Improve the ROS documentation? Support our educational efforts like the Diversity Scholars Program? Now you can choose!

We’re always thankful for your support, whether it’s monetary or a quick pull request! And remember, the OSRF is a 501(c)(3) tax-deductible charitable organization in the US.

If you, your colleagues, or your employer would like to support the OSRF and its mission, you can make a one-time or monthly donation using the new page. Many employers match charitable donations during the holiday season, so be sure to check if yours does. Here at Intrinsic, we’ve used our employee match program to raise almost $15,000 for the OSRF. We’d love to see other members of the ROS community join the effort.

Finally, please help us spread the word! Our Open Robotics community is huge, and if we all pitched in just a little bit we could make some amazing things happen in 2025.

Thank you for your support, and have a wonderful holiday season!

4 posts - 4 participants

Read full topic

Hi All,

We just wrapped up our monthly Gazebo community meeting and I want to share the recording. This month we had 8 participants from the NASA Space ROS Summer Sprint Challenge come and share their work. The results were absolutely exceptional and I figured it would be worth cross-posting the video to ROS Discourse.

November 2024 Gazebo Community Meeting: NASA SpaceROS Summer Sprint Challenge...

1 post - 1 participant

Read full topic

Have you ever had the intrusive thought of taking your IIWA off its mounts to see what would happen?

So you can spare your funds :

3 posts - 2 participants

Read full topic

Please come and join us for this coming meeting at 2024-12-02T17:00:00Z UTC→2024-12-02T18:00:00Z UTC , which will be a group setup session! We will be working together to set up Eclipse Zenoh to try out its features and performance. If you’re passionate about robotics or the cloud, come and say hello. We also plan to discuss the latest news from the group and from the world of Cloud Robotics.

Last meeting was a general catch-up session. If you’re interested to see the meeting recording, we have published it on YouTube.

If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on YouTube with our other meeting recordings too!

The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

Very pleased to share that ROS 2 Whisper just had a big upgrade. The action server now supports live-time transcription, see below:

This fantastic work was done by NathanCorral.

Go check it out at GitHub - ros-ai/ros2_whisper: Whisper C++ Inference Action Server for ROS 2

1 post - 1 participant

Read full topic

Hi,

To me, TCPROS is an example of open protocol - it provides specification, you can implement its own client and communicate with any ROS1 nodes over it.

DDS is also example of open protocol - it provides specification, you can implement its own client and communicate with any ROS2 nodes over it (examples of such clients are FastDDS, CycloneDDS, …).

Since Zenoh stands for “Zero Overhead Network Protocol” I was looking for any specification how this protocol works but could not find any.

Could someone point me please for such specification or if it does not exist would it mean that it is “closed protocol” and users can communicate with it only through clients which only Zenoh itself provides?

This seems important, as I could see that ROS leaning towards Zenoh to be default RMW in future (especially after watching ROSCon2024 )

Just to summarize: If Zenoh is open protocol, could someone point me please for its specification

Thank you,

6 posts - 5 participants

Read full topic

ROS News for the Week of November 18th, 2024

The ROSCon 2024 videos are finally here! If you missed a talk or missed the whole event you can now catch up by watching the videos online.

Join us on 2024-11-27 for our monthly Gazebo Community Meeting. We’ll have eight competitors from the NASA Space ROS Summer Sprint Challenge on to talk about their work.

@cottsay, one of our fantastic ROS core contributors, just added a new automatic review tool to rosdistro that should make it faster and easier to get your pull requests approved. Learn all about it in this post or by watching this ROSCon lightning talk.

Check out this homebrew ROS 2 snow plowing robot by Serdar Abali in Finland! With winter fast approaching in the northern hemisphere this seems like an amazing project! Coming across cool DIY ROS projects like this always makes my day.

Events

• 2024-11-27 Gazebo Community Meeting – Space ROS Summer Sprint Challenge
• 2024-12-02 Space Station OS Meeting 12pm JST/ 7am PST
• 2024-12-03 ROSCon Germany
• 2024-12-05 ROSCon India
• 2024-12-07 Circuit Launch Mountain View Grand Opening
• 2024-12-07 → 2024-12-08 ROSCon China in Shenzhen
• 2024-12-11 => 2024-12-12 Humanoids Summit Bay Area
• 2024-12-15 FIRA Ag Robotics Hackathon Registration Deadline
• 2024-12-16 => 2024-12-19 F1Tenth Sim Racing League at CDC 2024
• 2024-12-22 Open Hardware Summit CFP Deadline
• 2024-12-31 Deadline for Natural Robotics Contest
• 2025-02-01 FOSDEM 25 – See Robotics and Sim Room
• 2025-02-04 => 2025-02-06 World FIRA Ag Robotics Conference in Toulouse, France
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh

News

• Seegrid joins OSRA
• DIY ROS 2 Snow Removal Robot in Finland
• Bringing robot skills from simulation to the real world
• Adaptive morphing for stable, resilient, and energy-efficient flight of avian-informed drones
• Cyobot v2 Open Hardware Quadruped
• Four Growers builds robots to help solve greenhouse labor shortages
• Another boring SMACC demo in IsaacSim
• FreeCAD 1.0 Release – Sizzle Reel
• OpenCV Live: The Best Stuff from ROSCon 2024
• TRUMPF & Intrinsic: AI-enabled robotics for the machine tool industry
• Dave Coleman on Audrow Nash Podcast
• Teleo wants to help the robotics industry reach its ‘ChatGPT moment’
• Video Friday
• New Robot Sensor Modality?
• Red Cat beats Skydio for Drone Contract
• Pickle Robot gets orders for over 30 unloading systems plus $50M in funding
• Collaborative Robotics unveils Proxie mobile manipulator
• ZettaScale designs Zenoh to transcend DDS for automotive, ROS communications

ROS

• ROSCon 2024 Videos and Slides
• New Automation for Validating rosdistro Changes
• October TGC Meeting Minutes
• A Python Package that helps you generate ROS 2 Packages
• Simplifying AI Integration in UAVs: Challenges, Ideas, and Community Solutions
• 0 New and 47 Updated Noetic Packages
• 43 New and 347 Updated Packages for Jazzy
• ROS PMC Meeting Minutes for 2024-11-19
• Further Development of the ROS ABB Driver
• ROS Embodied AI Community Group
• Reference implementation of Zenoh-pico to micro-ROS
• Auto Car ROS 2 Vehicle Simulator
• Floor Plan Based Active Global Localization and Navigation Aid for Persons with Blindness
• 30 Different Image Matching Techniques in One Repository
• Fault Tolerant FogROS2
• ROS Voice Assistant
• Unlocking for Industrial Users the Power of ROS 2: ROS-I October Training Highlights

Got a Minute?

@DLu just sent over this amazing custom RViz panel tutorial to the ROS 2 documentation. We should all be more like @DLu and spend some time porting and updating ROS 1 Wiki articles to the ROS 2 documentation.

2 posts - 1 participant

Read full topic

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 22nd of October, 2024, were approved in the November meeting and are now available in the official minutes repository. You can find the complete minutes here.

The TGC received the usual project and technical committee updates, including the release of Gazebo Ionic, collaboration between Open-RMF and Gazebo to include Open-RMF functionality in the Gazebo Ionic demonstration world, and notice of the Infrastructure project preparing to move to Ubuntu 24.04.

In existing business, the Open-RMF PMC made a proposal to move the Nexus project under the purview of the Open-RMF PMC, due to the overlap in developers and the complementary nature of the features. The TGC agreed to make this recommendation to the OSRF Board.

In new business, the TGC discussed the pros and cons of versioning the data stored in rosbags, and of OSRF projects adopting Bazel. No decisions were made.

The next TGC meeting will take place on the 19th of December. The minutes of the November meeting should be approved in that meeting and posted publicly shortly thereafter.

5 posts - 3 participants

Read full topic

Hello there everyone!

We’re happy to announce 43 new packages and 347 updates are now available in ROS 2 Jazzy Jalisco .

This sync was tagged as jazzy/2024-11-21 .

Added Packages [43]:

• ros-jazzy-ess-imu-driver2: 2.0.2-1
• ros-jazzy-irobot-create-common-bringup: 3.0.4-1
• ros-jazzy-irobot-create-gz-bringup: 3.0.4-1
• ros-jazzy-irobot-create-gz-sim: 3.0.4-1
• ros-jazzy-irobot-create-gz-toolbox: 3.0.4-1
• ros-jazzy-irobot-create-nodes: 3.0.4-1
• ros-jazzy-plansys2-core: 2.0.14-1
• ros-jazzy-plansys2-domain-expert: 2.0.14-1
• ros-jazzy-plansys2-executor: 2.0.14-1
• ros-jazzy-plansys2-lifecycle-manager: 2.0.14-1
• ros-jazzy-plansys2-msgs: 2.0.14-1
• ros-jazzy-plansys2-pddl-parser: 2.0.14-1
• ros-jazzy-plansys2-planner: 2.0.14-1
• ros-jazzy-plansys2-popf-plan-solver: 2.0.14-1
• ros-jazzy-plansys2-problem-expert: 2.0.14-1
• ros-jazzy-plansys2-support-py: 2.0.14-1
• ros-jazzy-plansys2-tools: 2.0.14-1
• ros-jazzy-pose-broadcaster: 4.16.0-1
• ros-jazzy-ptz-action-server-msgs: 2.0.3-1
• ros-jazzy-raspimouse-description: 2.0.0-1
• ros-jazzy-rt-usb-9axisimu-driver: 3.0.0-1
• ros-jazzy-sbg-driver: 3.2.0-1
• ros-jazzy-simple-grasping: 0.5.0-1
• ros-jazzy-turtlebot4-gz-bringup: 2.0.2-1
• ros-jazzy-turtlebot4-simulator: 2.0.2-1

Updated Packages [347]:

• ros-jazzy-ackermann-steering-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-admittance-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-backward-ros: 1.0.5-1 → 1.0.6-1
• ros-jazzy-bicycle-steering-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-camera-calibration: 5.0.4-1 → 5.0.5-1
• ros-jazzy-control-msgs: 5.2.0-1 → 5.3.0-1
• ros-jazzy-control-toolbox: 3.2.0-3 → 3.3.0-1
• ros-jazzy-controller-interface: 4.18.0-1 → 4.20.0-1
• ros-jazzy-controller-manager: 4.18.0-1 → 4.20.0-1
• ros-jazzy-controller-manager-msgs: 4.18.0-1 → 4.20.0-1
• ros-jazzy-costmap-queue: 1.3.2-1 → 1.3.3-1
• ros-jazzy-depth-image-proc: 5.0.4-1 → 5.0.5-1
• ros-jazzy-diff-drive-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-dwb-core: 1.3.2-1 → 1.3.3-1
• ros-jazzy-dwb-critics: 1.3.2-1 → 1.3.3-1
• ros-jazzy-dwb-msgs: 1.3.2-1 → 1.3.3-1
• ros-jazzy-dwb-plugins: 1.3.2-1 → 1.3.3-1
• ros-jazzy-effort-controllers: 4.15.0-1 → 4.16.0-1
• ros-jazzy-fastrtps: 2.14.1-1 → 2.14.3-1
• ros-jazzy-force-torque-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
• ros-jazzy-forward-command-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-foxglove-compressed-video-transport: 1.0.0-1 → 1.0.1-1
• ros-jazzy-generate-parameter-library: 0.3.8-4 → 0.3.9-1
• ros-jazzy-generate-parameter-library-example: 0.3.8-4 → 0.3.9-1
• ros-jazzy-generate-parameter-library-py: 0.3.8-4 → 0.3.9-1
• ros-jazzy-generate-parameter-module-example: 0.3.8-4 → 0.3.9-1
• ros-jazzy-gripper-controllers: 4.15.0-1 → 4.16.0-1
• ros-jazzy-gz-common-vendor: 0.0.5-1 → 0.0.7-1
• ros-jazzy-gz-math-vendor: 0.0.6-1 → 0.0.7-1
• ros-jazzy-gz-msgs-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-physics-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-rendering-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-ros2-control: 1.2.7-1 → 1.2.8-1
• ros-jazzy-gz-ros2-control-demos: 1.2.7-1 → 1.2.8-1
• ros-jazzy-gz-sensors-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-sim-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-tools-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-hardware-interface: 4.18.0-1 → 4.20.0-1
• ros-jazzy-hardware-interface-testing: 4.18.0-1 → 4.20.0-1
• ros-jazzy-image-pipeline: 5.0.4-1 → 5.0.5-1
• ros-jazzy-image-proc: 5.0.4-1 → 5.0.5-1
• ros-jazzy-image-publisher: 5.0.4-1 → 5.0.5-1
• ros-jazzy-image-rotate: 5.0.4-1 → 5.0.5-1
• ros-jazzy-image-view: 5.0.4-1 → 5.0.5-1
• ros-jazzy-imu-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
• ros-jazzy-irobot-create-control: 3.0.3-1 → 3.0.4-1
• ros-jazzy-irobot-create-description: 3.0.3-1 → 3.0.4-1
• ros-jazzy-irobot-create-gz-plugins: 3.0.3-1 → 3.0.4-1
• ros-jazzy-irobot-create-toolbox: 3.0.3-1 → 3.0.4-1
• ros-jazzy-joint-limits: 4.18.0-1 → 4.20.0-1
• ros-jazzy-joint-state-broadcaster: 4.15.0-1 → 4.16.0-1
• ros-jazzy-joint-trajectory-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-joy-teleop: 1.6.0-1 → 1.7.0-1
• ros-jazzy-key-teleop: 1.6.0-1 → 1.7.0-1
• ros-jazzy-kinematics-interface: 1.1.0-1 → 1.2.1-1
• ros-jazzy-kinematics-interface-kdl: 1.1.0-1 → 1.2.1-1
• ros-jazzy-laser-filters: 2.0.7-3 → 2.0.8-1
• ros-jazzy-leo: 3.0.3-1 → 3.0.4-1
• ros-jazzy-leo-bringup: 1.4.0-3 → 2.0.0-1
• ros-jazzy-leo-description: 3.0.3-1 → 3.0.4-1
• ros-jazzy-leo-fw: 1.4.0-3 → 2.0.0-1
• ros-jazzy-leo-gz-bringup: 2.0.0-1 → 2.0.1-1
• ros-jazzy-leo-gz-plugins: 2.0.0-1 → 2.0.1-1
• ros-jazzy-leo-gz-worlds: 2.0.0-1 → 2.0.1-1
• ros-jazzy-leo-msgs: 3.0.3-1 → 3.0.4-1
• ros-jazzy-leo-robot: 1.4.0-3 → 2.0.0-1
• ros-jazzy-leo-simulator: 2.0.0-1 → 2.0.1-1
• ros-jazzy-leo-teleop: 3.0.3-1 → 3.0.4-1
• ros-jazzy-microstrain-inertial-description: 4.4.0-1 → 4.5.0-1
• ros-jazzy-microstrain-inertial-driver: 4.4.0-1 → 4.5.0-1
• ros-jazzy-microstrain-inertial-examples: 4.4.0-1 → 4.5.0-1
• ros-jazzy-microstrain-inertial-msgs: 4.4.0-1 → 4.5.0-1
• ros-jazzy-microstrain-inertial-rqt: 4.4.0-1 → 4.5.0-1
• ros-jazzy-mouse-teleop: 1.6.0-1 → 1.7.0-1
• ros-jazzy-mp2p-icp: 1.6.2-1 → 1.6.3-1
• ros-jazzy-mrpt-apps: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libapps: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libbase: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libgui: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libhwdrivers: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libmaps: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libmath: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libnav: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libobs: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libopengl: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libposes: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libros-bridge: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libslam: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mrpt-libtclap: 2.14.3-1 → 2.14.5-1
• ros-jazzy-mvsim: 0.11.0-1 → 0.11.1-1
• ros-jazzy-nav-2d-msgs: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav-2d-utils: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-amcl: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-behavior-tree: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-behaviors: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-bringup: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-bt-navigator: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-collision-monitor: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-common: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-constrained-smoother: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-core: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-costmap-2d: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-dwb-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-graceful-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-lifecycle-manager: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-loopback-sim: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-map-server: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-mppi-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-msgs: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-navfn-planner: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-planner: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-rotation-shim-controller: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-rviz-plugins: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-simple-commander: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-smac-planner: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-smoother: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-system-tests: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-theta-star-planner: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-util: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-velocity-smoother: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-voxel-grid: 1.3.2-1 → 1.3.3-1
• ros-jazzy-nav2-waypoint-follower: 1.3.2-1 → 1.3.3-1
• ros-jazzy-navigation2: 1.3.2-1 → 1.3.3-1
• ros-jazzy-novatel-gps-driver: 4.1.3-1 → 4.2.0-1
• ros-jazzy-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1
• ros-jazzy-octomap-msgs: 2.0.0-5 → 2.0.1-1
• ros-jazzy-odom-to-tf-ros2: 1.0.2-4 → 1.0.3-2
• ros-jazzy-opennav-docking: 1.3.2-1 → 1.3.3-1
• ros-jazzy-opennav-docking-bt: 1.3.2-1 → 1.3.3-1
• ros-jazzy-opennav-docking-core: 1.3.2-1 → 1.3.3-1
• ros-jazzy-openni2-camera: 2.2.1-1 → 2.2.2-1
• ros-jazzy-openvdb-vendor: 2.5.2-1 → 2.5.3-1
• ros-jazzy-parallel-gripper-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-parameter-traits: 0.3.8-4 → 0.3.9-1
• ros-jazzy-pcl-conversions: 2.6.1-4 → 2.6.2-1
• ros-jazzy-pcl-ros: 2.6.1-4 → 2.6.2-1
• ros-jazzy-perception-pcl: 2.6.1-4 → 2.6.2-1
• ros-jazzy-pid-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-pose-cov-ops: 0.3.12-1 → 0.3.13-1
• ros-jazzy-position-controllers: 4.15.0-1 → 4.16.0-1
• ros-jazzy-python-mrpt: 2.14.3-1 → 2.14.5-1
• ros-jazzy-range-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
• ros-jazzy-realtime-tools: 2.6.0-1 → 2.8.1-1
• ros-jazzy-robot-calibration: 0.9.1-1 → 0.9.2-1
• ros-jazzy-robot-calibration-msgs: 0.9.1-1 → 0.9.2-1
• ros-jazzy-ros-babel-fish: 0.9.3-1 → 0.10.0-1
• ros-jazzy-ros-babel-fish-test-msgs: 0.9.3-1 → 0.10.0-1
• ros-jazzy-ros-gz: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros-gz-bridge: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros-gz-image: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros-gz-interfaces: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros-gz-sim: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros-gz-sim-demos: 1.0.5-1 → 1.0.7-1
• ros-jazzy-ros2-control: 4.18.0-1 → 4.20.0-1
• ros-jazzy-ros2-control-test-assets: 4.18.0-1 → 4.20.0-1
• ros-jazzy-ros2-controllers: 4.15.0-1 → 4.16.0-1
• ros-jazzy-ros2-controllers-test-nodes: 4.15.0-1 → 4.16.0-1
• ros-jazzy-ros2controlcli: 4.18.0-1 → 4.20.0-1
• ros-jazzy-rqt-controller-manager: 4.18.0-1 → 4.20.0-1
• ros-jazzy-rqt-image-overlay: 0.3.1-4 → 0.4.0-1
• ros-jazzy-rqt-image-overlay-layer: 0.3.1-4 → 0.4.0-1
• ros-jazzy-rqt-joint-trajectory-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-scenario-execution: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-control: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-coverage: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-gazebo: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-interfaces: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-nav2: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-os: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-py-trees-ros: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-ros: 1.2.0-4 → 1.2.0-5
• ros-jazzy-scenario-execution-x11: 1.2.0-4 → 1.2.0-5
• ros-jazzy-sdformat-vendor: 0.0.6-1 → 0.0.7-1
• ros-jazzy-spatio-temporal-voxel-layer: 2.5.2-1 → 2.5.3-1
• ros-jazzy-steering-controllers-library: 4.15.0-1 → 4.16.0-1
• ros-jazzy-stereo-image-proc: 5.0.4-1 → 5.0.5-1
• ros-jazzy-teleop-tools: 1.6.0-1 → 1.7.0-1
• ros-jazzy-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1
• ros-jazzy-test-ros-gz-bridge: 1.0.5-1 → 1.0.7-1
• ros-jazzy-tracetools-image-pipeline: 5.0.4-1 → 5.0.5-1
• ros-jazzy-transmission-interface: 4.18.0-1 → 4.20.0-1
• ros-jazzy-tricycle-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-tricycle-steering-controller: 4.15.0-1 → 4.16.0-1
• ros-jazzy-turtlebot4-base: 2.0.0-1 → 2.0.1-2
• ros-jazzy-turtlebot4-bringup: 2.0.0-1 → 2.0.1-2
• ros-jazzy-turtlebot4-diagnostics: 2.0.0-1 → 2.0.1-2
• ros-jazzy-turtlebot4-gz-gui-plugins: 2.0.1-1 → 2.0.2-1
• ros-jazzy-turtlebot4-gz-toolbox: 2.0.1-1 → 2.0.2-1
• ros-jazzy-turtlebot4-robot: 2.0.0-1 → 2.0.1-2
• ros-jazzy-turtlebot4-setup: 2.0.1-1 → 2.0.2-1
• ros-jazzy-turtlebot4-tests: 2.0.0-1 → 2.0.1-2
• ros-jazzy-twist-stamper: 0.0.3-4 → 0.0.5-1
• ros-jazzy-ur: 2.4.12-1 → 2.4.13-1
• ros-jazzy-ur-calibration: 2.4.12-1 → 2.4.13-1
• ros-jazzy-ur-controllers: 2.4.12-1 → 2.4.13-1
• ros-jazzy-ur-dashboard-msgs: 2.4.12-1 → 2.4.13-1
• ros-jazzy-ur-moveit-config: 2.4.12-1 → 2.4.13-1
• ros-jazzy-ur-robot-driver: 2.4.12-1 → 2.4.13-1
• ros-jazzy-velocity-controllers: 4.15.0-1 → 4.16.0-1
• ros-jazzy-velodyne: 2.3.0-4 → 2.5.1-1
• ros-jazzy-velodyne-driver: 2.3.0-4 → 2.5.1-1
• ros-jazzy-velodyne-laserscan: 2.3.0-4 → 2.5.1-1
• ros-jazzy-velodyne-msgs: 2.3.0-4 → 2.5.1-1
• ros-jazzy-velodyne-pointcloud: 2.3.0-4 → 2.5.1-1

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

• Addisu Z. Taddese
• Aditya Pande
• Alberto Tudela
• Alejandro Hernandez
• Alejandro Hernández
• Alexey Merzlyakov
• Bence Magyar
• Bernd Pfrommer
• Brian Wilcox
• Carl Delsey
• Carlos Orduno
• Chris Iverach-Brereton
• David V. Lu!!
• Denis Štogl
• Ekumen
• Enrique Fernandez
• Felix Exner
• Fictionlab
• Francisco Martin Rico
• Frederik Pasch
• George Stavrinos
• Intel Labs
• Jon Binney
• Jose-Luis Blanco-Claraco
• Josh Newans
• Josh Whitley
• Matej Vargovcik
• Michael Ferguson
• Michael Jeronimo
• Miguel Company
• Mohammad Haghighipanah
• P. J. Reed
• Paul Bovbel
• Paul Gesel
• RT Corporation
• Raymond Chow
• Rob Fisher
• Robert Wilbrandt
• SBG Systems
• Stefan Fabian
• Steve Macenski
• Tim Clephas
• Tyler Weaver
• Victor López
• Vincent Rabaud
• Víctor Mayoral-Vilches
• Wolfgang Merkt
• ijnek
• paul
• rkreinin
• steve
• steve macenski

Enjoy!

1 post - 1 participant

Read full topic