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."

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

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.

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

We’re happy to announce 0 new packages and 19 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-03-20.

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

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [19]:

• ros-noetic-costmap-cspace: 0.17.5-1 → 0.17.6-1
• ros-noetic-depthai-bridge: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-descriptions: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-examples: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-filters: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros-driver: 2.11.0-1 → 2.11.2-1
• ros-noetic-depthai-ros-msgs: 2.11.0-1 → 2.11.2-1
• ros-noetic-joystick-interrupt: 0.17.5-1 → 0.17.6-1
• ros-noetic-map-organizer: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation-common: 0.17.5-1 → 0.17.6-1
• ros-noetic-neonavigation-launch: 0.17.5-1 → 0.17.6-1
• ros-noetic-obj-to-pointcloud: 0.17.5-1 → 0.17.6-1
• ros-noetic-planner-cspace: 0.17.5-1 → 0.17.6-1
• ros-noetic-safety-limiter: 0.17.5-1 → 0.17.6-1
• ros-noetic-track-odometry: 0.17.5-1 → 0.17.6-1
• ros-noetic-trajectory-tracker: 0.17.5-1 → 0.17.6-1
• ros-noetic-ur-client-library: 1.7.1-1 → 1.8.0-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:

• Adam Serafin
• Atsushi Watanabe
• Felix Exner

1 post - 1 participant

Read full topic

Hello guys,
It has been now 2 weeks that I use the new gazebo version (gz) and wow is the doc unhelpfull. Every time I search some thing I find the old version tutorial…
I have a few examples for example :

• I want to know how to use the mesh tag in my .world file and the only tutorial that I found is Pavillon CustomWorld from ArticulatedRobotics.
• How do I use the size tag ? Is it applicable for every geometry ?
• I want to import uri no good explanation how to do it (yes there is a tutorial but it’s not intuitive…
  And a lot more…

I am not here to just say this is bad but I want to know if other people feel lost like me and how can we change this situation ?

Hope I don’t make to many people angry !

5 posts - 5 participants

Read full topic

OSRF Google Summer of Code 2025

Hi Everyone,

I am excited to announce that all of our Google Summer of Code (GSoC) projects for 2025 are now available online in our GSoC Wiki. If you are unfamiliar with GSoC, it is a summer internship program sponsored by Google that is open to undergraduate and graduate students in most countries (see video below). The GSoC program allows students to work with veteran open source developers over the summer to contribute to open source projects.

This year, all five Open Robotics projects (ROS, Gazebo, Open-RMF, ROS Infrastructure, and ROS Control) will participate in GSoC. This will be our only internship opportunity this year, so we made sure to recruit as many mentors as possible. We will also be posting an open internship thread on ROS Discourse in the next couple days.

2025 Open Robotics Projects

This year we will offer sixteen GSoC projects across our five open source projects. These projects will be mentored or co-mentored by sixteen seasoned contributors from the Open Robotics community. I’ve summarized the projects below, but you can read all about them on our project wiki page.

• Gazebo:
  • Gazebo GPU Lidar with @arjo129
  • Gazebo Gaussian Splats with @arjo129
  • Physics-based sonar simulation with @woensug-choi, @rakeshv24, and @mabelzhang
• Open-RMF:
  • Improving UI / UX of Site Editor with @grey and Xiyu Oh
  • Workflow Diagram Editor with @grey and @Luca
  • Multi-Agent Traffic Optimization with @grey and @Luca
  • New Open-RMF Demo Demo with @Aaron_Chong
• ROS:
  • Improved ROS 2 Doctor with @tomoyafujita
  • Structured Parameter Support with @JM_ROS
  • C/C++ Struct to ROS Message Converter with @JM_ROS
  • Improvements to ROS 2 Tracing @christophebedard
• ROS Infrastructure:
  • VCSTool Improvements with @claraberendsen and @jrivero
  • Mixin composition in colcon-mixin with @cottsay and Sean McGrath
  • SDFormat on PyPi with @jrivero
• ROS Control:
  • Mission Control for ROS 2 Control with @bmagyar and @saikishor
  • Hardware Diagnostic Support with @bmagyar and @saikishor

Project Proposals

Student applications for GSoC will be open from 2025-03-24T07:00:00Z UTC→2025-04-08T07:00:00Z UTC. Students must apply using the application form on the official GSoC website.

After speaking with our mentors I want to call out a few things that we’re looking for in student applications. Students applying to our GSoC projects should make sure to highlight the following things in their application:

• We want to see your work, even if it’s not perfect! Please include projects from school, work, or personal initiatives. Include links to your GitHub/GitLab profile and/or a personal project page. We’re looking for students who actively code and improve their skills.
• We prefer students with some open source experience. If you’ve contributed to a FOSS project, or an Open Robotics project, please call that out. We want to see that you are familiar with the process of submitting a pull request to an open source project and working with the maintainer to get that pull request merged. These don’t have to be big pull requests, a single line or character change is fine!
• If you have experience with one of our projects, like ROS or Gazebo, please mention that! Classroom experience is more than sufficient. If you have been to a ROS event (either in person, or virtual) call that out! We’re looking for students who are active ROS users and part of the broader ROS community.
• Our mentors are looking for students with strong written communication skills. Our GSoC students will spend the summer mostly communicating with their mentors via written communications. It is important that students are able to express themselves clearly and succinctly. We ask that students not use large language models to write their project proposals, however using an LLM to check grammar and spelling is acceptable. Our mentors may choose to reject students they suspect used LLMs to write their applications.

Finally, the best way to enhance your GSoC proposal is to connect with our mentors and the ROS community. Consider submitting a pull request to one of our projects. Most Open Robotics project repositories have “Good First Issue” and “Help Wanted” tags in their issue trackers. If you have time, please consider making a small project contribution. For guidance, feel free to join our Discord server.

2 posts - 1 participant

Read full topic

docs.ros.org Got a Facelift!

Hi everyone,

If you’re anything like me, you probably visit docs.ros.org at least five times a day, and you probably also have at least two dozen bookmarks related to ROS development in your browser. It seems like a good portion of onboarding new ROS users is just pointing them to the ROS documentation and our useful resources.

I’ve been trying to fix this problem for quite a while, and I finally have some good news! Thanks to some wonderful open-source design contributions from Shak and Vlad at HelloRobo.co, we’ve put together a new landing page for the ROS documentation. This new landing page should be your one-stop shop for most of your ROS documentation resources, and it renders well on mobile devices!

Don’t worry, the page still points you to the same ROS documentation, but we’ve managed to include just about everything you could need on one handy page! On the new docs.ros.org page, you’ll find:

• The documentation for every ROS release
• Pointers to our ROS calendars and how to add your events
• Links to all of our community resources (Discord, Discourse, Robotics Stack Exchange)
• Links to the ROS distro art and trademark information
• All of our ROS and ROSCon videos on Vimeo
• Links to ROS REPs and ROS package information
• An at-a-glance installation guide for new users
• A whole lot more!

If there’s something you think we missed that belongs there, please don’t hesitate to reach out or send us a pull request.

And thanks again Vlad and Shak for contributing their design skills to the project! And thanks @Nuclearsandwich with the deployment help.

10 posts - 7 participants

Read full topic

Hi everyone,

I’m exploring the idea of using GPS sensor exclusively to guide a mobile robot along predefined line patterns on sports fields (such as soccer fields, tracks, or basketball courts). The goal is to rely solely on GPS data for navigation—without the use of cameras, vision systems, or any additional sensors. Is it possible?

My main objective here is to investigate the weaknesses and limitations of using only GPS for precise navigation. This exploration could serve as a foundation for later expansion by incorporating multiple sensors or technologies, but for now, I want to focus on how far GPS alone can take us.

9 posts - 7 participants

Read full topic

ROS Noetic is reaching End of Life in May 2025 – Which additional packages do you need in ROS Noetic ESM?

With ROS Noetic and Ubuntu 20.04 approaching EOL, their Extended Security Maintenance (ESM) period begins in April-May this year. During this time, ROS packages inside Ubuntu’s ROS ESM repository will continue receiving five more years of security updates, alongside Ubuntu Main. This is crucial for companies that must comply with security regulations but aren’t ready to migrate to a newer ROS or Ubuntu distribution yet.

Canonical would like to know which Noetic packages are essential for you to be included in our ESM.

Right now for each ROS distribution entering its ESM phase, we include:

• REP-142 ‘ros_base’ for ROS 1
• REP-2001 ‘ros_base’ for ROS 2

We follow a structured process, similar to Ubuntu’s Main Inclusion Process, to ensure long-term support for these packages.

This is your chance to let us know which additional packages you need.

You can use this form, it should take less than 5 minutes! Survey Form

Remember that ROS ESM is available with the Ubuntu Pro subscription – and anyone can use Ubuntu Pro for free with up to 5 machines!

3 posts - 3 participants

Read full topic

Hi,

The next meeting of the Client Library Working Group will be this Friday, 21st March 2025 at 8 AM Pacific Time.

• Meeting link: https://meet.google.com/oij-atzj-znw
• Meeting minutes and agenda: ROS 2 Client Libraries Working Group - Google Docs
• Calendar invite: https://calendar.app.google/2LNP3u8tdffvyCPXA
• Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg

We are currently pushing the rclpy implementation to the finish line.
There’s currently some test issues that are being worked on and that we should discuss if not resolved by Friday.

Besides that, there’s also an interesting discussion about the expected behavior of the rclpp events executor EventsExecutor with an overrunning timer can lead to a burst of timer events · Issue #2771 · ros2/rclcpp · GitHub

Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!

1 post - 1 participant

Read full topic

Officially, ubuntu 22.04 is the tier1 platform for ros2 humble.

But nvidia isaac-ros team has migrated the version to ubuntu 20.04(for their jetson devices), which makes ros2 foxy, galactic and humble available in apt-get in one platform. This supports both amd64 and aarch64, only in ubuntu20.04.

Just sharing this rarely known info

# add isaac-ros repo
wget -qO - https://isaac.download.nvidia.com/isaac-ros/repos.key | sudo apt-key add -
echo "deb [arch=$(dpkg --print-architecture)] https://isaac.download.nvidia.com/isaac-ros/ubuntu/main $(lsb_release -cs) main" | sudo tee -a /etc/apt/sources.list

# add ros2 repo
sudo apt update && sudo apt install curl -y
sudo curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o /usr/share/keyrings/ros-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu $(. /etc/os-release && echo $UBUNTU_CODENAME) main" | sudo tee /etc/apt/sources.list.d/ros2.list > /dev/null

# install ros2
sudo apt-get update
sudo apt install ros-humble-desktop
sudo apt install ros-humble-ros-base
sudo apt install ros-dev-tools

# more tests
lsb_release -as
ape-cache search yaml-cpp
ape-cache search isaac-ros
sudo apt install ros-humble-isaac-ros-nitros

5 posts - 2 participants

Read full topic

[ROS Amazing Contributor Badge]

I am honored and grateful to have received the prestigious ‘ROS Amazing Contributor Badge’ an accolade granted to only 20 individuals globally by the ROS community.

The ROS Contributor Badge is categorized into three levels—Contributor, Great Contributor, and Amazing Contributor—based on the number of pull requests submitted to the official ROS GitHub repositories, verified by the ROS Discourse community. Currently, there are 535 Contributors, 126 Great Contributors, and only 20 Amazing Contributors worldwide.

ROS is a robotic software development platform that holds significant meaning for me. Since my first encounter with ROS 1 Diamondback in 2011, I have consistently utilized ROS in research and development projects for over 15 years. My Master’s and Ph.D. studies centered around ROS, and it remains an essential development tool at ROBOTIS, where I am currently employed. Additionally, I have attended ROSCon nine times between 2014 and 2022, including presenting at ROSCon 2016.

Moreover, in collaboration with Open Robotics, I contributed to developing TurtleBot3, a ROS standard platform robot launched officially in 2017. TurtleBot3 is an official Open Robotics brand, and ROBOTIS contributes part of the TurtleBot3 sales revenue back to Open Robotics. Thus, every TurtleBot3 user is significantly contributing to the growth of the ROS ecosystem.

Furthermore, I have authored nine ROS-related books translated into English, Japanese, Chinese, and Korean, including “Robot Programming with ROS 2” (Korean edition). I served as a ROS Technical Steering Committee (TSC) member from 2018 to 2019, helping guide the community’s future, and have organized approximately 60 ROS-related seminars, actively promoting the open-source community.

During the ROS 1 Kinetic era, I maintained 154 out of the 2,051 official ROS packages. Although I had slowed down in recent years, I resumed actively developing public packages again this year, regularly updating ROS 2 packages and planning further contributions beneficial to the community.

This ‘ROS Amazing Contributor Badge’ has given me an opportunity to reflect on my journey and deepened my passion for the ROS community. I look forward to continuing my contributions to help many individuals positively impact the robotics industry through ROS.

Furthermore, we are continuing active development not only on TurtleBot3, OpenManipulator, DYNAMIXEL, and Delivery Service Robot (GAEMI) but also advancing leader, follower, and humanoid robots utilizing manipulators essential for the era of Physical AI. Please stay tuned for future developments.

Thanks, Open Robotics and ROS Community. I ROS.

https://discourse.ros.org/badges/107/amazing-contributor

2 posts - 2 participants

Read full topic

The ROS MeetUp is coming to Cali, Colombia!

Enjoy an afternoon of inspiring talks about ROS / ROS 2, connect with developers, researchers, students, and robotics enthusiasts, and take the opportunity to exchange ideas.

When? May 24, 2025, from 3:00 to 7:00 pm.

Where? Universidad Santiago de Cali, Pedro Elías Serrano Auditorium.

How to participate? Register for the event as an attendee here.

Want to share your experience? Apply to speak here. (Until May 4th)

Come share, learn, and be part of this experience!

1 post - 1 participant

Read full topic

Please come and join us for this coming meeting at 2025-03-24T17:00:00Z UTC→2025-03-24T18:00:00Z UTC, where we will have a general catch-up, review our progress as a group, and discuss a new option for some meetings going forward: determining a meeting topic in advance and spending the meeting discussing that topic.

Last meeting, the group had a general catch-up and spent the session discussing their preferences and issues with the most popular deployment methods. We agreed that distribution via Docker containers was our preferred method, but that it still had issues, and we also discussed a possible project to remotely disable particular functions of a robot. If you want to watch for yourself, the recording is available 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 or keep an eye on the Cloud Robotics Hub.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

Intro

The Robot Operating System (ROS) is an essential platform for developing robotic applications. However, getting ROS up and running on various systems can be challenging due to issues like dependency conflicts, varying operating system versions, and hardware inconsistencies.

One way to simplify this is by using Docker, which allows you to containerize your ROS environment. This method provides a portable, isolated environment that can be shared across different machines without affecting your host system.

In this guide, we will walk through the process of setting up ROS Noetic inside a Docker container and using it to:

1. Run ROS Noetic in Docker.
2. Simulate a mobile robot using Gazebo.
3. Control the robot with teleop_twist_keyboard.
4. Customize launch files for different simulation environments.

Benefits of Using Docker for ROS:

• Consistency: Docker ensures the environment is the same across all systems.
• Portability: Easily share and deploy ROS applications without worrying about installation or configuration.
• Cross-Platform: Works on Linux, macOS, and Windows, providing flexibility.
• Isolation: Keeps your ROS environment separate from your host system, minimizing conflicts.

For more about Docker, visit the official Docker documentation.

Setting Up ROS Noetic in Docker

To begin, you need Docker installed on your machine. If you haven’t installed Docker yet, follow the official guide to install Docker.

Run a ROS Noetic Docker Container in your Windows Terminal

Start by pulling the official ROS Noetic image and running it in an interactive terminal:

docker run -it --name ros_container --net=host --privileged osrf/ros:noetic-desktop-full bash

Explanation of Parameters:

• docker run -it: Launches the container in interactive mode.
• --name ros_container: Assigns a custom name to the container for easy reference.
• --net=host: Ensures that ROS nodes can communicate with each other on the same network as the host.
• --privileged: Grants the container full access to the host’s devices, which is necessary for simulation.
• osrf/ros:noetic-desktop-full: Uses the ROS Noetic image, which includes the desktop version with tools like Gazebo.

Once you execute this command, you’ll be inside the Docker container, where ROS Noetic is fully set up and ready to use.

Creating a ROS Workspace and Building Packages

A ROS workspace is essential for organizing your projects and packages. Here’s how you can set up a basic workspace:

Create and Build a Catkin Workspace

mkdir -p ~/Workspaces/smb_ws/src
cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Running a Robot Simulation in Gazebo

To test ROS in a real-world scenario, we will simulate a Small Mobile Robot (SMB) in Gazebo, a popular robot simulation tool integrated with ROS.

Clone the SMB Simulation Repository

cd ~/Workspaces/smb_ws/src
git clone https://github.com/ethz-asl/smb_common.git

Build the Package

cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Launch the Simulation

roslaunch smb_gazebo smb_gazebo.launch

Controlling the Robot with Teleoperation

To manually control the simulated robot, we’ll use the teleop_twist_keyboard package, which allows control via keyboard input.

Clone and Build the Teleoperation Package

cd ~/Workspaces/smb_ws/src
git clone https://github.com/ros-teleop/teleop_twist_keyboard.git
cd ~/Workspaces/smb_ws
catkin_make
source devel/setup.bash

Run the Teleoperation Node

rosrun teleop_twist_keyboard teleop_twist_keyboard.py

Use the W/A/S/D keys to move the robot forward, backward, left, and right, and the Q/E keys to rotate it.

Verifying and Debugging ROS Nodes

As with any ROS application, debugging is an essential part of development.
Here are some common commands to verify the status of your ROS nodes and topics.

Check Running ROS Nodes

rosnode list

Check Available ROS Topics

rostopic list

Publish Velocity Commands Manually

To control the robot directly via command line, you can publish velocity command

rostopic pub -r 10 /cmd_vel geometry_msgs/Twist '{linear: {x: 0.5, y: 0.0, z: 0.0}, angular: {x: 0.0, y: 0.0, z: 0.5}}'

This command will move the robot forward while rotating it at a rate of 0.5 radians per second.

Conclusion

In this guide, we’ve set up ROS Noetic in Docker and demonstrated how to simulate a robot in Gazebo, control it manually.

Further Resources

• Docker Documentation
• ROS Noetic Documentation
• Gazebo Documentation
• Teleoperation Package on GitHub

If you have any feedback or questions, feel free to reach out through the ROS Discourse.

Hope this helps

5 posts - 4 participants

Read full topic

Hi folks!,

JdeRobot org is again participating in Google Summer of Code 2025. If you are a student or otherwise eligible to the GSoC program, we are seeking Robotics enthusiasts!. Just submit your application for one of our proposed projects, all of them using ROS2 , and typically Gazebo or Carla robotics simulators (this year even O3DE simulator!). For GSoC-2025 JdeRobot is mentoring projects about:

• RoboticsAcademy
• Robot programming tools (BT-STudio, VisualCircuit)
• AI driven Robotics

For more details about the projects and application submission, visit the JdeRobot GSoC 2025 page and our candidate selection process!

Take a look at some JdeRobot’s previous GSoC success stories such as those of Prajyot, Óscar or Pankaj.

1 post - 1 participant

Read full topic

I want to create a URDF for a mobile robot that can perform painting tasks exactly like in the video in below link. The robot needs to move around and apply paint to surfaces accurately in simulation.

The link: https://www.youtube.com/watch?v=cTrxOl3FSrA&pp=ygUJdHVyZiB0YW5r

I’m looking for guidance on:

1. Defining the robot’s structure in URDF (chassis, wheels, painting arm, etc.)
2. Adding actuators and joints for precise painting movement
3. Simulating the painting action in Gazebo or another simulator
4. Integrating sensors (e.g., cameras or LiDAR) for navigation and painting precision

Has anyone worked on something similar? Any tips, example URDFs, or relevant resources would be greatly appreciated!

8 posts - 7 participants

Read full topic

Hello everyone!

Happy Pi day!

We’re happy to announce 9 new package and 119 updates are now available in ROS 2 Rolling Ridley

This sync was tagged as rolling/2025-03-14 .

Package Updates for rolling

Added Packages [9]:

• ros-rolling-apriltag-detector-dbgsym: 3.0.1-2
• ros-rolling-apriltag-tools: 3.0.1-2
• ros-rolling-apriltag-tools-dbgsym: 3.0.1-2
• ros-rolling-nobleo-socketcan-bridge: 1.0.1-1
• ros-rolling-nobleo-socketcan-bridge-dbgsym: 1.0.1-1
• ros-rolling-pinocchio: 3.4.0-3
• ros-rolling-pinocchio-dbgsym: 3.4.0-3
• ros-rolling-rmw-desert: 2.0.0-1
• ros-rolling-rmw-desert-dbgsym: 2.0.0-1

Updated Packages [119]:

• ros-rolling-ackermann-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-ackermann-steering-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-admittance-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-admittance-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-apriltag-detector: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-detector-mit: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-detector-mit-dbgsym: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-detector-umich: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-detector-umich-dbgsym: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-draw: 2.0.0-1 → 3.0.1-2
• ros-rolling-apriltag-draw-dbgsym: 2.0.0-1 → 3.0.1-2
• ros-rolling-bicycle-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-bicycle-steering-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-control-msgs: 5.3.0-1 → 6.0.0-1
• ros-rolling-control-msgs-dbgsym: 5.3.0-1 → 6.0.0-1
• ros-rolling-control-toolbox: 4.0.1-1 → 5.0.0-1
• ros-rolling-control-toolbox-dbgsym: 4.0.1-1 → 5.0.0-1
• ros-rolling-controller-interface: 4.26.0-1 → 4.27.0-1
• ros-rolling-controller-interface-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-controller-manager: 4.26.0-1 → 4.27.0-1
• ros-rolling-controller-manager-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-controller-manager-msgs: 4.26.0-1 → 4.27.0-1
• ros-rolling-controller-manager-msgs-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-diff-drive-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-diff-drive-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-dynamixel-interfaces: 1.0.0-1 → 1.0.1-1
• ros-rolling-dynamixel-interfaces-dbgsym: 1.0.0-1 → 1.0.1-1
• ros-rolling-effort-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-effort-controllers-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-ffmpeg-image-transport: 1.0.1-1 → 1.0.2-1
• ros-rolling-ffmpeg-image-transport-dbgsym: 1.0.1-1 → 1.0.2-1
• ros-rolling-force-torque-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-rolling-force-torque-sensor-broadcaster-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-forward-command-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-forward-command-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-gpio-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-gpio-controllers-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-gripper-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-gripper-controllers-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-hardware-interface: 4.26.0-1 → 4.27.0-1
• ros-rolling-hardware-interface-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-hardware-interface-testing: 4.26.0-1 → 4.27.0-1
• ros-rolling-hardware-interface-testing-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-imu-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-rolling-imu-sensor-broadcaster-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-joint-limits: 4.26.0-1 → 4.27.0-1
• ros-rolling-joint-limits-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-joint-state-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-rolling-joint-state-broadcaster-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-joint-trajectory-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-joint-trajectory-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-kinematics-interface: 1.2.1-1 → 2.0.0-1
• ros-rolling-kinematics-interface-dbgsym: 1.2.1-1 → 2.0.0-1
• ros-rolling-kinematics-interface-kdl: 1.2.1-1 → 2.0.0-1
• ros-rolling-kinematics-interface-kdl-dbgsym: 1.2.1-1 → 2.0.0-1
• ros-rolling-mecanum-drive-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-mecanum-drive-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-message-filters: 7.0.1-1 → 7.0.2-1
• ros-rolling-message-filters-dbgsym: 7.0.1-1 → 7.0.2-1
• ros-rolling-metavision-driver: 2.0.0-1 → 2.0.1-1
• ros-rolling-metavision-driver-dbgsym: 2.0.0-1 → 2.0.1-1
• ros-rolling-openeb-vendor: 2.0.1-2 → 2.0.2-1
• ros-rolling-openeb-vendor-dbgsym: 2.0.1-2 → 2.0.2-1
• ros-rolling-parallel-gripper-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-parallel-gripper-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-pid-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-pid-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-pose-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-rolling-pose-broadcaster-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-position-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-position-controllers-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-range-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-rolling-range-sensor-broadcaster-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-rmw: 7.8.0-1 → 7.8.1-1
• ros-rolling-rmw-cyclonedds-cpp: 4.0.0-1 → 4.0.1-1
• ros-rolling-rmw-cyclonedds-cpp-dbgsym: 4.0.0-1 → 4.0.1-1
• ros-rolling-rmw-dbgsym: 7.8.0-1 → 7.8.1-1
• ros-rolling-rmw-fastrtps-cpp: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-fastrtps-cpp-dbgsym: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-fastrtps-dynamic-cpp: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-fastrtps-dynamic-cpp-dbgsym: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-fastrtps-shared-cpp: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-fastrtps-shared-cpp-dbgsym: 9.3.0-1 → 9.3.1-1
• ros-rolling-rmw-implementation: 3.0.3-1 → 3.0.4-1
• ros-rolling-rmw-implementation-cmake: 7.8.0-1 → 7.8.1-1
• ros-rolling-rmw-implementation-dbgsym: 3.0.3-1 → 3.0.4-1
• ros-rolling-rmw-security-common: 7.8.0-1 → 7.8.1-1
• ros-rolling-rmw-security-common-dbgsym: 7.8.0-1 → 7.8.1-1
• ros-rolling-ros2-control: 4.26.0-1 → 4.27.0-1
• ros-rolling-ros2-control-test-assets: 4.26.0-1 → 4.27.0-1
• ros-rolling-ros2-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-ros2-controllers-test-nodes: 4.20.0-1 → 4.21.0-1
• ros-rolling-ros2controlcli: 4.26.0-1 → 4.27.0-1
• ros-rolling-rosidl-typesupport-fastrtps-c: 3.7.1-1 → 3.7.1-3
• ros-rolling-rosidl-typesupport-fastrtps-c-dbgsym: 3.7.1-1 → 3.7.1-3
• ros-rolling-rosidl-typesupport-fastrtps-cpp: 3.7.1-1 → 3.7.1-3
• ros-rolling-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.7.1-1 → 3.7.1-3
• ros-rolling-rqt-controller-manager: 4.26.0-1 → 4.27.0-1
• ros-rolling-rqt-joint-trajectory-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-steering-controllers-library: 4.20.0-1 → 4.21.0-1
• ros-rolling-steering-controllers-library-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-transmission-interface: 4.26.0-1 → 4.27.0-1
• ros-rolling-transmission-interface-dbgsym: 4.26.0-1 → 4.27.0-1
• ros-rolling-tricycle-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-tricycle-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-tricycle-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-rolling-tricycle-steering-controller-dbgsym: 4.20.0-1 → 4.21.0-1
• ros-rolling-ur: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-calibration: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-calibration-dbgsym: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-controllers: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-controllers-dbgsym: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-dashboard-msgs: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-dashboard-msgs-dbgsym: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-moveit-config: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-robot-driver: 3.0.2-1 → 3.1.0-1
• ros-rolling-ur-robot-driver-dbgsym: 3.0.2-1 → 3.1.0-1
• ros-rolling-velocity-controllers: 4.20.0-1 → 4.21.0-1
• ros-rolling-velocity-controllers-dbgsym: 4.20.0-1 → 4.21.0-1

Removed Packages [6]:

• ros-rolling-autoware-lanelet2-extension
• ros-rolling-autoware-lanelet2-extension-dbgsym
• ros-rolling-autoware-lanelet2-extension-python
• ros-rolling-autoware-lanelet2-extension-python-dbgsym
• ros-rolling-autoware-utils
• ros-rolling-autoware-utils-dbgsym

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:

• Alejandro Hernandez Cordero
• Bence Magyar
• Bernd Pfrommer
• Brandon Ong
• Davide Costa
• Denis Štogl
• Erik Boasson
• Felix Exner
• Geoffrey Biggs
• Justin Carpentier
• Pyo
• Ramon Wijnands
• Shane Loretz
• William Woodall

I’d like to also call out that we’ve added 29 new and 350 updated arm64 packages.

1 post - 1 participant

Read full topic

Hi folks,

Not the most enjoyable news to receive on a Friday night but security notices are best acted on quickly. A popular re-usable GitHub Action tj-actions/changed-files has been compromised. There is a well written article with the details here: Semgrep | 🚨 Popular GitHub Action tj-actions/changed-files is compromised

The Infrastructure project and Open Robotics Security team are taking action in core Open Robotics repositories but I wanted to make sure that all in the community are aware and can take appropriate steps.

If I can soap box at all here, my recommendation when using platforms like GitHub Actions is to rely on what you know rather than what you can find for small tasks like this. Inlining your own change detection logic as recommended in the article is doable with a few lines of git and shell. Here’s one example from the reprepro-updater repository. The script there may not have the features of the reusable action but it’s plain what it does when you look at it and it will always do exactly that until you need to change it.

When it does make sense to rely on shared GitHub Actions, such as for more complicated tasks the other advice in the above article is worth heeding:

Generally, pin all GitHub Actions to specific commit SHAs (rather than version tags) you know are safe.

3 posts - 2 participants

Read full topic

ROS News for the Week of March 10th, 2025

NVIDIA GTC is next week. We’ve got a big after party planned that we’ve co-organized with our friends at Silicon Valley Robotics. Everyone is welcome to attend, even if you are not going to GTC!

If you are going to GTC, there is a robotics meetup that they’ve planned for Wednesday along with a handy list of robotics sessions at the event. (Note that you have to be a registered GTC attendee for both the meetup and the event list).

Our colleague @Pyo over at Robotis has put together a prototype that integrates Hugging Face’s LeRobot arm with the TurtleBot3 Burger. The combination is an affordable option for those looking for a mobile manipulator that supports teleop and RL training. Somewhat related, our friends at Seeed Studios have organized a LeRobot Hackathon for the weekend after GTC.

Events

• 2025-03-18 ROS By-The-Bay X Silicon Valley Robotics GTC After Party
• 2025-03-19 NVIDIA GTC Physical AI Developer Meetup (must have a GTC ticket to register).
• 2025-03-20 Aerial Robotics Meeting
• 2025-03-17 ==> 2025-03-21 ROS / Robotics Sessions at GTC
• 2025-03-22 Seeed Embodied AI Hackathon with LeRobot
• 2025-03-24 ROS Meetup at European Robotics Forum
• 2025-03-24 Intrinsic / Automatica Sponsored Fun Run at European Robotics Forum
• 2025-03-26 Dronecode Philly Meetup
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
• 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
• 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh

News

Here’s some good news: this week over 90 people joined the OSRA along with Heex.io. For new individual members we’ll be getting back to you shortly. Membership info is on our website.

• ROS PMC Minutes for 2025-03-12
• ROS users meet up at NVIDIA GTC 2025?
• Ros-controls PMC meeting 12th March 2025
• Why Vision Processing is Shifting Closer to the Sensor - Audrow Nash Podcast
• America Wastes $6+ Billion Worth Of Recyclables A Year. Can Robots and AI Help?
• Gemini Robotics brings AI into the physical world
  • IEEE Spectrum - Robot Report - TechCrunch
• Video Friday
• Singapore’s National Robotics Programme launches RoboNexus
• Dexterity picks up $95M in funding for container unloading robots
• Waymo was slapped with nearly 600 parking tickets last year in SF alone
• Yet another AI robotics firm lands major funding, as Dexterity closes latest round
• Video: Ridgeback with Two UR5e Arms on an Elevated Top Plate
• Video: Omnidirectional Mobile Manipulator with WheelBot in Isaac Sim, managed by Open-RMF via Zenoh
• Why is Gazebo very famous in the ROS community? what about Webots?
• FOSSASIA 2025 Live Stream
• Humanoid Robotics Masterclass The Construct (Paid)

ROS

• Low-cost LiDAR robot kit for beginners
• Hugging Face LeRobot with TurtleBot3
• Articulated Robotics: GPUs & Robots - The Easy Way
• Weekly Robotics is so back!
• Deep Reinforcement Learning for mobile robot navigation in ROS Gazebo simulator.
• The ROS Buildfarm Now Runs on 24.04
• Reusable Components in URDF
• Mobile Robot URDF Maker
• ROS 2 Jazzy Packages for Ubuntu 22.04
• GPS RTK Support for ROS 2 Jazzy – Any Recommended Wrappers or Drivers?
• Introducing obstacle avoidance function in Autoware
• LiDAR-RT: Gaussian-based Ray Tracing for Dynamic LiDAR Re-simulation CVPR 2025
• ROS 2 package for fusing 360° equirectangular images with 3D LiDAR data.
• PincOpen – A low cost and open source parallel-finger gripper, derived from Reachy 2’s gripper
• LIR-LIVO: A Lightweight,Robust Lidar/Vision/Inertial Odometry with Illumination-Resilient Deep Features
• ICRA2025: OpenGS-SLAM: Open-Set Dense Semantic SLAM with 3D Gaussian Splatting for Object-Level Scene Understanding
• ROS×Python Let’s implement parallel processing (Japanese)
• TRG-planner: Traversal Risk Graph-Based Path Planning in Unstructured Environments
• Open Source Mechatronics Course
• micro-ROS library for Platform.IO
• Livox MID-360 ROS 2 Driver for RoboRacer/ F1Tenth
• Simple, Cute, Open Hardware Robot Arm
• Self Docking Using April Tags in ROS 2
• Formula to optimize DDS communication performance in multi-robot systems.
• ROS Jazzy Crash Course at the Construct
• ROS package for LIDAR odometry with rotation optimization
• ROS 2 Dev Container

Got a Minute? / Appreciation

This is normally where I post a few issues that could use some community support.

Good news, all of my issues for this week have a new contributor working on them!

Here are a few things that have happened this week:

• Ever want to automagically set an environment variable in your ROS workspace? Github user @SuperGops7 just merged a pull request into docs.ros.org that shows you how to use Ament to set environment variables.
• Python type hinting in RCLPy is coming to a dev environment near you. @InvincibleRMC has a couple of PRs in flight.
  • We could really use some help reviewing these PRs to get them over the line.

3 posts - 2 participants

Read full topic

Hello,

I have designed, manufactured and made available commercially a (very) low-cost LiDAR robot kit for ROS2 beginners.

This is a little differential robot with 120mm base and a 2D LiDAR. The bot runs micro-ROS on ESP32 Arduino and ROS2/Nav2 Iron on a local PC. A product video short is available here.

This robot comes with a video instruction series explaining step-by-step, “from-scratch” the robot assembly, firmware and software setup, bring-up, mapping/SLAM, autonomous navigation and frontier exploration.

Extensive troubleshooting instructions and a technical support forum are available as a help resource.

I hope this kit can be useful for the ROS community.

1 post - 1 participant

Read full topic

I’m working on integrating a GPS RTK system into a robot running ROS 2 Jazzy, and I’m looking for RTK GPS solutions that are specifically built for this ROS 2 Jazzy.

So far, I’ve come across some general GPS RTK-compatible packages, but I’m wondering if there are any officially maintained drivers, wrappers, or recommended devices that work seamlessly with ROS 2 Jazzy?

6 posts - 5 participants

Read full topic

We’re happy to announce 32 new packages and 549 updates are now available in Jazzy Jalisco. This sync was tagged as jazzy/2025-03-10 .

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

Package Updates for jazzy

Note that package counts include dbgsym packages which have been filtered out from the list below

Added Packages [32]:

• ros-jazzy-apriltag-detector-mit: 3.0.1-1
• ros-jazzy-apriltag-detector-umich: 3.0.1-1
• ros-jazzy-apriltag-draw: 3.0.1-1
• ros-jazzy-apriltag-tools: 3.0.1-1
• ros-jazzy-dynamixel-interfaces: 1.0.0-1
• ros-jazzy-etsi-its-denm-ts-coding: 3.1.0-1
• ros-jazzy-etsi-its-denm-ts-conversion: 3.1.0-1
• ros-jazzy-etsi-its-denm-ts-msgs: 3.1.0-1
• ros-jazzy-hebi-cpp-api: 3.12.3-1
• ros-jazzy-mola-gnss-to-markers: 0.1.0-1
• ros-jazzy-nonpersistent-voxel-layer: 2.5.0-1
• ros-jazzy-novatel-oem7-driver: 24.0.0-1
• ros-jazzy-novatel-oem7-msgs: 24.0.0-1
• ros-jazzy-rmw-desert: 1.0.3-1
• ros-jazzy-synapticon-ros2-control: 0.1.2-1
• ros-jazzy-webots-ros2-crazyflie: 2025.0.0-1
• ros-jazzy-webots-ros2-husarion: 2025.0.0-1

Updated Packages [549]:

• ros-jazzy-ackermann-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-admittance-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-apriltag: 3.4.2-1 → 3.4.3-1
• ros-jazzy-apriltag-detector: 1.0.0-3 → 3.0.1-1
• ros-jazzy-automatika-ros-sugar: 0.2.6-1 → 0.2.9-1
• ros-jazzy-bicycle-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-camera-calibration: 5.0.6-1 → 5.0.9-1
• ros-jazzy-chomp-motion-planner: 2.12.1-1 → 2.12.2-1
• ros-jazzy-clearpath-config: 2.1.0-1 → 2.1.1-1
• ros-jazzy-coal: 3.0.0-1 → 3.0.1-1
• ros-jazzy-compressed-depth-image-transport: 4.0.3-1 → 4.0.4-1
• ros-jazzy-compressed-image-transport: 4.0.3-1 → 4.0.4-1
• ros-jazzy-control-toolbox: 4.0.0-1 → 4.0.1-1
• ros-jazzy-controller-interface: 4.25.0-1 → 4.27.0-1
• ros-jazzy-controller-manager: 4.25.0-1 → 4.27.0-1
• ros-jazzy-controller-manager-msgs: 4.25.0-1 → 4.27.0-1
• ros-jazzy-costmap-queue: 1.3.4-1 → 1.3.5-1
• ros-jazzy-depth-image-proc: 5.0.6-1 → 5.0.9-1
• ros-jazzy-depthai-bridge: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-descriptions: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-examples: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-filters: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-ros: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-ros-driver: 2.10.5-1 → 2.11.0-1
• ros-jazzy-depthai-ros-msgs: 2.10.5-1 → 2.11.0-1
• ros-jazzy-diagnostic-aggregator: 4.2.1-1 → 4.2.2-1
• ros-jazzy-diagnostic-common-diagnostics: 4.2.1-1 → 4.2.2-1
• ros-jazzy-diagnostic-updater: 4.2.1-1 → 4.2.2-1
• ros-jazzy-diagnostics: 4.2.1-1 → 4.2.2-1
• ros-jazzy-diff-drive-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-ds-dbw: 2.3.1-1 → 2.3.2-1
• ros-jazzy-ds-dbw-can: 2.3.1-1 → 2.3.2-1
• ros-jazzy-ds-dbw-joystick-demo: 2.3.1-1 → 2.3.2-1
• ros-jazzy-ds-dbw-msgs: 2.3.1-1 → 2.3.2-1
• ros-jazzy-dwb-core: 1.3.4-1 → 1.3.5-1
• ros-jazzy-dwb-critics: 1.3.4-1 → 1.3.5-1
• ros-jazzy-dwb-msgs: 1.3.4-1 → 1.3.5-1
• ros-jazzy-dwb-plugins: 1.3.4-1 → 1.3.5-1
• ros-jazzy-dynamixel-sdk: 3.7.40-6 → 3.8.1-1
• ros-jazzy-dynamixel-sdk-custom-interfaces: 3.7.40-6 → 3.8.1-1
• ros-jazzy-dynamixel-sdk-examples: 3.7.40-6 → 3.8.1-1
• ros-jazzy-dynamixel-workbench-msgs: 2.0.3-5 → 2.1.0-1
• ros-jazzy-effort-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-eigenpy: 3.8.2-1 → 3.10.3-1
• ros-jazzy-etsi-its-cam-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cam-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cam-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cam-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cam-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cam-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cpm-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cpm-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-cpm-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-denm-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-denm-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-denm-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-mapem-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-mapem-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-mapem-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-messages: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-msgs-utils: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-primitives-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-rviz-plugins: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-spatem-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-spatem-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-spatem-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-vam-ts-coding: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-vam-ts-conversion: 3.0.0-1 → 3.1.0-1
• ros-jazzy-etsi-its-vam-ts-msgs: 3.0.0-1 → 3.1.0-1
• ros-jazzy-ffmpeg-image-transport: 1.0.1-2 → 1.0.2-1
• ros-jazzy-force-torque-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-jazzy-forward-command-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-foxglove-msgs: 3.0.0-3 → 3.1.0-1
• ros-jazzy-gpio-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-gripper-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-gz-cmake-vendor: 0.0.8-1 → 0.0.9-1
• ros-jazzy-gz-common-vendor: 0.0.7-1 → 0.0.8-1
• ros-jazzy-gz-fuel-tools-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-gui-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-launch-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-math-vendor: 0.0.7-1 → 0.0.8-1
• ros-jazzy-gz-msgs-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-physics-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-plugin-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-gz-rendering-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-ros2-control: 1.2.10-1 → 1.2.11-1
• ros-jazzy-gz-ros2-control-demos: 1.2.10-1 → 1.2.11-1
• ros-jazzy-gz-sensors-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-sim-vendor: 0.0.7-1 → 0.0.8-1
• ros-jazzy-gz-tools-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-transport-vendor: 0.0.5-1 → 0.0.6-1
• ros-jazzy-gz-utils-vendor: 0.0.4-1 → 0.0.5-1
• ros-jazzy-hardware-interface: 4.25.0-1 → 4.27.0-1
• ros-jazzy-hardware-interface-testing: 4.25.0-1 → 4.27.0-1
• ros-jazzy-hls-lfcd-lds-driver: 2.0.4-6 → 2.1.0-1
• ros-jazzy-image-pipeline: 5.0.6-1 → 5.0.9-1
• ros-jazzy-image-proc: 5.0.6-1 → 5.0.9-1
• ros-jazzy-image-publisher: 5.0.6-1 → 5.0.9-1
• ros-jazzy-image-rotate: 5.0.6-1 → 5.0.9-1
• ros-jazzy-image-transport-plugins: 4.0.3-1 → 4.0.4-1
• ros-jazzy-image-view: 5.0.6-1 → 5.0.9-1
• ros-jazzy-imu-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-jazzy-joint-limits: 4.25.0-1 → 4.27.0-1
• ros-jazzy-joint-state-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-jazzy-joint-trajectory-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-kitti-metrics-eval: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mecanum-drive-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-message-filters: 4.11.3-1 → 4.11.4-1
• ros-jazzy-mola: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-bridge-ros2: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-demos: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-imu-preintegration: 1.6.1-1 → 1.7.0-1
• ros-jazzy-mola-input-euroc-dataset: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-kitti-dataset: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-kitti360-dataset: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-mulran-dataset: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-paris-luco-dataset: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-rawlog: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-input-rosbag2: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-kernel: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-launcher: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-lidar-odometry: 0.6.1-1 → 0.7.0-1
• ros-jazzy-mola-metric-maps: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-msgs: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-pose-list: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-relocalization: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-state-estimation: 1.6.1-1 → 1.7.0-1
• ros-jazzy-mola-state-estimation-simple: 1.6.1-1 → 1.7.0-1
• ros-jazzy-mola-state-estimation-smoother: 1.6.1-1 → 1.7.0-1
• ros-jazzy-mola-traj-tools: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-viz: 1.6.0-1 → 1.6.2-1
• ros-jazzy-mola-yaml: 1.6.0-1 → 1.6.2-1
• ros-jazzy-moveit: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-common: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-configs-utils: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-core: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-hybrid-planning: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-kinematics: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-planners: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-planners-chomp: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-planners-ompl: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-planners-stomp: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-plugins: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-py: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-resources-prbt-ikfast-manipulator-plugin: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-resources-prbt-moveit-config: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-resources-prbt-pg70-support: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-resources-prbt-support: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-benchmarks: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-control-interface: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-move-group: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-occupancy-map-monitor: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-perception: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-planning: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-planning-interface: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-robot-interaction: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-tests: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-trajectory-cache: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-visualization: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-ros-warehouse: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-runtime: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-servo: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-app-plugins: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-assistant: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-controllers: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-core-plugins: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-framework: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-setup-srdf-plugins: 2.12.1-1 → 2.12.2-1
• ros-jazzy-moveit-simple-controller-manager: 2.12.1-1 → 2.12.2-1
• ros-jazzy-mp2p-icp: 1.6.5-1 → 1.6.6-1
• ros-jazzy-mvsim: 0.13.1-1 → 0.13.2-1
• ros-jazzy-nav-2d-msgs: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav-2d-utils: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-amcl: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-behavior-tree: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-behaviors: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-bringup: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-bt-navigator: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-collision-monitor: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-common: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-constrained-smoother: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-core: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-costmap-2d: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-dwb-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-graceful-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-lifecycle-manager: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-loopback-sim: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-map-server: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-mppi-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-msgs: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-navfn-planner: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-planner: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-rotation-shim-controller: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-rviz-plugins: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-simple-commander: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-smac-planner: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-smoother: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-system-tests: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-theta-star-planner: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-util: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-velocity-smoother: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-voxel-grid: 1.3.4-1 → 1.3.5-1
• ros-jazzy-nav2-waypoint-follower: 1.3.4-1 → 1.3.5-1
• ros-jazzy-navigation2: 1.3.4-1 → 1.3.5-1
• ros-jazzy-ntrip-client-node: 0.5.4-1 → 0.5.5-3
• ros-jazzy-opennav-docking: 1.3.4-1 → 1.3.5-1
• ros-jazzy-opennav-docking-bt: 1.3.4-1 → 1.3.5-1
• ros-jazzy-opennav-docking-core: 1.3.4-1 → 1.3.5-1
• ros-jazzy-pal-statistics: 2.6.1-1 → 2.6.2-1
• ros-jazzy-pal-statistics-msgs: 2.6.1-1 → 2.6.2-1
• ros-jazzy-pangolin: 0.9.1-3 → 0.9.3-1
• ros-jazzy-parallel-gripper-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-pid-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-pilz-industrial-motion-planner: 2.12.1-1 → 2.12.2-1
• ros-jazzy-pilz-industrial-motion-planner-testutils: 2.12.1-1 → 2.12.2-1
• ros-jazzy-pose-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-jazzy-position-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-qml-ros2-plugin: 1.0.1-1 → 1.25.2-2
• ros-jazzy-range-sensor-broadcaster: 4.20.0-1 → 4.21.0-1
• ros-jazzy-realtime-tools: 3.3.0-1 → 3.4.0-1
• ros-jazzy-rmw-zenoh-cpp: 0.2.1-1 → 0.2.2-1
• ros-jazzy-ros-babel-fish: 0.10.3-1 → 2.25.2-1
• ros-jazzy-ros-babel-fish-test-msgs: 0.10.3-1 → 2.25.2-1
• ros-jazzy-ros-gz: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros-gz-bridge: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros-gz-image: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros-gz-interfaces: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros-gz-sim: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros-gz-sim-demos: 1.0.7-1 → 1.0.9-1
• ros-jazzy-ros2-control: 4.25.0-1 → 4.27.0-1
• ros-jazzy-ros2-control-test-assets: 4.25.0-1 → 4.27.0-1
• ros-jazzy-ros2-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-ros2-controllers-test-nodes: 4.20.0-1 → 4.21.0-1
• ros-jazzy-ros2controlcli: 4.25.0-1 → 4.27.0-1
• ros-jazzy-rosapi: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosapi-msgs: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosbridge-library: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosbridge-msgs: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosbridge-server: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosbridge-suite: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rosbridge-test-msgs: 2.1.0-1 → 2.2.0-1
• ros-jazzy-rqt-controller-manager: 4.25.0-1 → 4.27.0-1
• ros-jazzy-rqt-joint-trajectory-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-rqt-plot: 1.4.0-2 → 1.4.2-1
• ros-jazzy-rtabmap: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-conversions: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-demos: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-examples: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-launch: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-msgs: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-odom: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-python: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-ros: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-rviz-plugins: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-slam: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-sync: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-util: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rtabmap-viz: 0.21.9-1 → 0.21.10-1
• ros-jazzy-rviz-satellite: 4.1.0-1 → 4.1.0-2
• ros-jazzy-sdformat-vendor: 0.0.8-1 → 0.0.9-1
• ros-jazzy-self-test: 4.2.1-1 → 4.2.2-1
• ros-jazzy-septentrio-gnss-driver: 1.4.1-1 → 1.4.2-1
• ros-jazzy-simple-launch: 1.10.1-1 → 1.11.0-1
• ros-jazzy-steering-controllers-library: 4.20.0-1 → 4.21.0-1
• ros-jazzy-stereo-image-proc: 5.0.6-1 → 5.0.9-1
• ros-jazzy-test-ros-gz-bridge: 1.0.7-1 → 1.0.9-1
• ros-jazzy-theora-image-transport: 4.0.3-1 → 4.0.4-1
• ros-jazzy-topic-tools: 1.3.2-1 → 1.3.3-1
• ros-jazzy-topic-tools-interfaces: 1.3.2-1 → 1.3.3-1
• ros-jazzy-tracetools-image-pipeline: 5.0.6-1 → 5.0.9-1
• ros-jazzy-transmission-interface: 4.25.0-1 → 4.27.0-1
• ros-jazzy-tricycle-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-tricycle-steering-controller: 4.20.0-1 → 4.21.0-1
• ros-jazzy-turtlebot3-msgs: 2.2.1-5 → 2.3.0-1
• ros-jazzy-turtlebot4-setup: 2.0.2-1 → 2.0.3-1
• ros-jazzy-ublox-dgnss: 0.5.4-1 → 0.5.5-3
• ros-jazzy-ublox-dgnss-node: 0.5.4-1 → 0.5.5-3
• ros-jazzy-ublox-nav-sat-fix-hp-node: 0.5.4-1 → 0.5.5-3
• ros-jazzy-ublox-ubx-interfaces: 0.5.4-1 → 0.5.5-3
• ros-jazzy-ublox-ubx-msgs: 0.5.4-1 → 0.5.5-3
• ros-jazzy-ur: 3.0.2-1 → 3.1.0-1
• ros-jazzy-ur-calibration: 3.0.2-1 → 3.1.0-1
• ros-jazzy-ur-client-library: 1.6.0-1 → 1.7.1-1
• ros-jazzy-ur-controllers: 3.0.2-1 → 3.1.0-1
• ros-jazzy-ur-dashboard-msgs: 3.0.2-1 → 3.1.0-1
• ros-jazzy-ur-moveit-config: 3.0.2-1 → 3.1.0-1
• ros-jazzy-ur-robot-driver: 3.0.2-1 → 3.1.0-1
• ros-jazzy-velocity-controllers: 4.20.0-1 → 4.21.0-1
• ros-jazzy-velodyne-description: 2.0.3-4 → 2.0.4-1
• ros-jazzy-webots-ros2: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-control: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-driver: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-epuck: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-importer: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-mavic: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-msgs: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-tesla: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-tests: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-tiago: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-turtlebot: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-webots-ros2-universal-robot: 2023.1.3-1 → 2025.0.0-1
• ros-jazzy-wireless-msgs: 1.1.2-1 → 1.1.3-1
• ros-jazzy-wireless-watcher: 1.1.2-1 → 1.1.3-1
• ros-jazzy-yasmin: 3.0.3-1 → 3.1.0-1
• ros-jazzy-yasmin-demos: 3.0.3-1 → 3.1.0-1
• ros-jazzy-yasmin-msgs: 3.0.3-1 → 3.1.0-1
• ros-jazzy-yasmin-ros: 3.0.3-1 → 3.1.0-1
• ros-jazzy-yasmin-viewer: 3.0.3-1 → 3.1.0-1
• ros-jazzy-zenoh-cpp-vendor: 0.2.1-1 → 0.2.2-1
• ros-jazzy-zstd-image-transport: 4.0.3-1 → 4.0.4-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:

• Adam Serafin
• Addisu Z. Taddese
• Aditya Pande
• Alberto Tudela
• Alejandro Hernandez
• Alejandro Hernandez Cordero
• Alejandro Hernández
• Alexander Gutenkunst
• Alexey Merzlyakov
• Andre Schröder
• Austin Hendrix
• Automatika Robotics
• Bence Magyar
• Bernd Pfrommer
• Blake Anderson
• Brandon Ong
• Brian Wilcox
• Błażej Sowa
• Carl Delsey
• Carlos Orduno
• Chittaranjan Srinivas Swaminathan
• Chris Bollinger
• Chris Iverach-Brereton
• Christian Henkel
• Cyberbotics
• David V. Lu!!
• Davide Costa
• Elevate Robotics
• Emerson Knapp
• Felix Exner
• Foxglove
• Geoff Sokoll
• Geoffrey Biggs
• Henning Kayser
• Husarion
• Jean-Pierre Busch
• Jordan Palacios
• Jose Luis Blanco-Claraco
• Jose-Luis Blanco-Claraco
• Joseph Mirabel
• José Luis Blanco-Claraco
• Justin Carpentier
• Kenji Brameld
• Kevin Hallenbeck
• Kimberly McGuire (Bitcraze AB)
• Luis Camero
• Matej Vargovcik
• Mathieu Labbe
• Max Krogius
• Michael Görner
• Michael Jeronimo
• Miguel Ángel González Santamarta
• Mohammad Haghighipanah
• MoveIt Release Team
• Nick Hortovanyi
• NovAtel Support
• Olivier Kermorgant
• Peter David Fagan
• Pyo
• Roni Kreinin
• Stefan Fabian
• Steve Macenski
• Steven Lovegrove
• Steven Macenski
• Tibor Dome
• Vincent Rabaud
• Víctor Mayoral-Vilches
• Yadunund
• miguel
• rkreinin
• steve
• steve macenski

Enjoy!

1 post - 1 participant

Read full topic

In the robotics course at our university, we were taught using Webots. Although the docs felt kinda dated, but it was a neat simulator.

Now that I’m getting started in ROS, Gazebo’s name comes up everywhere, it even has its own chat channels, forum category and place in the official docs.

Webots also supports ROS2 and is also FOSS.

So, what’s there in Gazebo that’s not in Webots? And what’s unliked in Webots that is not the case in Gazebo?

18 posts - 10 participants

Read full topic

ROS News for the Week of March 3rd, 2025

The 2024 ROS Metrics Report has been released. We’re happy to report that ROS community continues to grow and the vast majority of ROS users have moved on to ROS 2. New this year we’ve added some basic contributor metrics from Github.

OSRA Membership badges went out this week and the internet was full - of - people showing their support. If you would like to join the OSRA and support ROS, Gazebo, Open-RMF, ROS Controls, and the infrastructure we all depend on, you can do so using this form the OSRA website.

Our colleague @rkent has done a ton of work improving the end-user experience of ROS Index. This week we pushed a couple of updates that make the search experience both faster and more accurate. Thanks a lot @rkent!

Check out this amazing project where the Turtlebot 3 navigates with deep reinforcement learning.

Events

• 2025-03-10 ROS 2 Rust Meeting
• 2025-03-10 Open-RMF: Community Forum
• 2025-03-11 ROS-Industrial Training (Americas)
• 2025-03-11 Space ROS Club Japan
• 2025-03-17 ==> 2025-03-21 ROS / Robotics Sessions at GTC
• 2025-03-18 ROS By-The-Bay X Silicon Valley Robotics NVIDIA GTC Meetup
• 2025-03-18 Custom flight modes using PX4 and ROS 2
• 2025-03-19 NVIDIA GTC Physical AI Developer Meetup (must have a GTC ticket to register).
• 2025-03-24 ROS Meetup at #ERF2025
• 2025-04-20 Due Date: OpenCV / Intrinsic Perception Challenge for Bin-picking
• 2025-04-28 International Workshop on Robotics Software Engineering
• 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
• 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
• 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
• 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh

News

• 2024 ROS Metrics Report
• Clutterbot has joined the OSRA
• OSRA Member Viam announces $30M Series C – The Robot Report
• WebRTC Video in Transitive Robotics
• Any info of ROS 3(found ros3.org website)?
• ICRA Space Manipulation Workshop
• Get ready for ROS 1 sunset and learn ROS 2 features at the Robotics Summit
• Turtle Robots: Embodied design for enhanced flipper-based locomotion in complex terrains
• Legged Locomotion Meets Skateboarding
• IEEE RAS CASE Travel Grants
• ‘Flow’ wins best animated feature film Oscar using open source software
• ABB plans to invest $120M to expand production capacity in the U.S.
• Aescape raises $83M to bring robotic massager to more locations
• ARM Institute announces new project call, RoboticsCareer.org employer capabilities
• Alibaba-backed robotics firm LimX completes $69m series A
• Robot Videos: Atlas in the Lab, Unitree Kung Fu, and More - IEEE Spectrum

ROS

• TurtleBot 4 Now Supports ROS 2 Jazzy
• Migration of build.ros2.org to Ubuntu 24.04
• New packages for ROS 2 Rolling Ridley
• New Packages for ROS 1 Noetic Ninjemys
• Turtlebot 3 Deep Reinforcement Learning Navigation
• Webots simulation of Spot with ROS 2
• Link inertia tests for robot manipulator URDF - robot description formats
• Pika: A Fast Data Collector Solution for Embodied Intelligence
• Announcing: rviz_robot_description_topic
• Video: Interop SIG March 6, 2025: Memory-safe High-performance Async ROS Programming
• Video: Customize and configure the rmf-web dashboard with MicroApps
• Video: Cracow Robotics & AI Club #10
• Video: Customize and configure the rmf-web dashboard with MicroApps
• Video: The Experience at the Dronecode San Diego Meetup
• Video: 2025 Winter Robotics Colloquium: Sebastian Castro (Robotics and AI Institute)
• Video: Robotic locomotion through active and passive morphological adaptation
• Nav2: Support for Error Codes and (New) Error Messages!
• Behavior Tree library alternative to SMACH and FlexBE
• Quadrotor-Based Slung Payload Transportation Gazebo SITL Simulation Package V1.0
• Flight Control Code For Quadrotors Carrying A Tethered Payload
• Open-source Resources And Tutorials for Drone Tracking
• ROS 2 package for fusing 360° equirectangular images with 3D LiDAR data.
• C++/CUDA library for Multi-View Stereo
• ROLO: ROS package for lidar odometry implementation using rotation optimization method.
• ROScribe: Write your robot software in minutes.
• RT CRANE+ V2 ROS 2 package for Jazzy
• RT CRANE-X7 ROS 2 package Jazzy
• A Unified Self-Driving World Model for Simultaneous 3D Scene Understanding and Generation
• Open ROS Components for Robots from Fetch: sensor and deformable UMI fingers
• Real-Time Dense SLAM with 3D Reconstruction Priors
• EgoMimic: Georgia Tech PhD student uses Project Aria Research Glasses to help train humanoid robots
• FACTR: Force-Attending Curriculum Training for Contact-Rich Policy Learning

Got a minute ?

We seem to have a problem where RCLPy’s quality of service API documentation is not rendering on docs.ros.org. We’re looking for someone who can contribute a few hours and figure out the issue. The core team would really appreciate some help with this issue.

1 post - 1 participant

Read full topic

Hello ROS Community,

The OSRF Infrastructure Project is planning to migrate https://build.ros2.org to new servers based on Ubuntu 24.04, as part of our ongoing efforts to maintain and improve the ROS buildfarm infrastructure. To facilitate this migration, the following services will experience downtime during the maintenance window:

• https://build.ros2.org (Jenkins) will be temporarily unavailable or in shutdown mode (not running jobs).

• https://repo.ros2.org will be temporarily unavailable.

• https://packages.ros.org will remain accessible during this time, so it will still be possible to perform package updates and installation using the official ROS repositories.

• In order to reduce churn while the build farm is offline for migration, all rosdistro PRs will be held for the week and merged after the migration completes.

The migration is scheduled to begin on Tuesday 2025-03-11T12:00:00Z UTC (12:00 UTC) and is expected to last for 8-12 hours. During this time, the buildfarm will be offline, and all queued jobs will need to complete before Jenkins is taken offline for the data transfer. Given the large volume of build artifacts and log files to transfer, we are planning for a full workday of downtime to ensure a smooth transition.

Once the migration is complete, I’ll update this thread to confirm that services are back online. I’ll also be monitoring for any issues that may arise as a result of the migration.

Thank you for your patience as we work to improve the ROS buildfarm infrastructure. If you have any questions or concerns, please feel free to reach out in this thread.

Att,

Cristóbal

7 posts - 2 participants

Read full topic

Pika: Fast Data Collector Solution for Embodied Intelligence #embodiedai #robot

Introducing Pika: A Fast Data Collector Solution for Embodied Intelligence

I’m excited to share AgileX Robotics latest contribution to robotics research—a fast, robust data collection solution named Pika. Designed with the needs of embodied intelligence in mind, Pika minimizes setup time while maximizing performance, making it an ideal tool for both research and rapid prototyping.

Key Features
Streamlined Two-Step Clamp Mechanism:
Transition from power-on to operational mode instantly. Our innovative clamp design eliminates lengthy calibration, ensuring that your robot is ready for action in virtually zero preparation time.

Zero Latency & Maximum Efficiency:
The system’s ultra-synchronized motion control ensures smooth, real-time data capture. This means you can reliably record dynamic movements with precision—critical when working on high-performance robotics projects.

Lightweight & Ergonomic:
Pika’s design is optimized for continuous operation. Its featherlight construction not only reduces the overall load but also allows for seamless integration into existing robotic systems, enhancing your workflow without adding unnecessary complexity.

Why Pika Stands Out
Insta-Ready Setup:
Eliminate the need for time-consuming calibrations and adjustments. Get straight to data collection and experiment iterations faster than ever.

Precision & Reliability:
Enjoy high-precision measurements with a system that maintains performance even in fast-paced research environments.

Ideal for Rapid Innovation:
Whether you’re training AI models or deploying robotic systems in the field, Pika is built to support the rigorous demands of modern robotics research.

For more details, please visit the AgileX website.

Looking forward to your feedback and discussions on integrating Pika into your projects!

1 post - 1 participant

Read full topic

Hello everyone!

It took a minute but we’re happy to announce 20 new package and 254 updates are now available in ROS 2 Rolling Ridley

Among the new packages is fastdds which was renamed from fastrtps and more importantly bumped to v3.1.2 which is now utilized by rmw_fastrtps

This sync was tagged as rolling/2025-03-06 .

Package Updates for rolling

Added Packages [20]:

• ros-rolling-boost-sml-vendor: 1.1.11-1
• ros-rolling-dynamixel-interfaces: 1.0.0-1
• ros-rolling-dynamixel-interfaces-dbgsym: 1.0.0-1
• ros-rolling-fastdds: 3.1.2-2
• ros-rolling-fastdds-dbgsym: 3.1.2-2
• ros-rolling-hebi-cpp-api: 3.12.3-1
• ros-rolling-hebi-cpp-api-dbgsym: 3.12.3-1
• ros-rolling-mola-gnss-to-markers: 0.1.0-1
• ros-rolling-mola-gnss-to-markers-dbgsym: 0.1.0-1
• ros-rolling-moveit-servo: 2.13.0-1
• ros-rolling-moveit-servo-dbgsym: 2.13.0-1
• ros-rolling-rmw-security-common: 7.8.0-1
• ros-rolling-rmw-security-common-dbgsym: 7.8.0-1
• ros-rolling-synapticon-ros2-control: 0.1.2-1
• ros-rolling-synapticon-ros2-control-dbgsym: 0.1.2-1
• ros-rolling-ur: 3.0.2-1
• ros-rolling-ur-moveit-config: 3.0.2-1
• ros-rolling-ur-simulation-gz: 2.1.0-1
• ros-rolling-webots-ros2-crazyflie: 2025.0.0-1
• ros-rolling-webots-ros2-husarion: 2025.0.0-1

Updated Packages [254]:

• ros-rolling-apriltag: 3.4.2-1 → 3.4.3-1
• ros-rolling-apriltag-dbgsym: 3.4.2-1 → 3.4.3-1
• ros-rolling-automatika-ros-sugar: 0.2.6-1 → 0.2.9-1
• ros-rolling-automatika-ros-sugar-dbgsym: 0.2.6-1 → 0.2.9-1
• ros-rolling-camera-calibration: 6.0.9-1 → 6.0.10-1
• ros-rolling-chomp-motion-planner: 2.12.0-1 → 2.13.0-1
• ros-rolling-chomp-motion-planner-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-coal: 3.0.0-1 → 3.0.1-1
• ros-rolling-coal-dbgsym: 3.0.0-1 → 3.0.1-1
• ros-rolling-depth-image-proc: 6.0.9-1 → 6.0.10-1
• ros-rolling-depth-image-proc-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-dynamixel-workbench-msgs: 2.0.3-4 → 2.1.0-1
• ros-rolling-dynamixel-workbench-msgs-dbgsym: 2.0.3-4 → 2.1.0-1
• ros-rolling-eigenpy: 3.8.2-1 → 3.10.3-1
• ros-rolling-eigenpy-dbgsym: 3.8.2-1 → 3.10.3-1
• ros-rolling-gz-cmake-vendor: 0.2.1-1 → 0.2.2-1
• ros-rolling-gz-common-vendor: 0.2.2-1 → 0.2.3-1
• ros-rolling-gz-common-vendor-dbgsym: 0.2.2-1 → 0.2.3-1
• ros-rolling-gz-fuel-tools-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-fuel-tools-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-gui-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-gui-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-launch-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-launch-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-math-vendor: 0.2.2-1 → 0.2.3-1
• ros-rolling-gz-math-vendor-dbgsym: 0.2.2-1 → 0.2.3-1
• ros-rolling-gz-physics-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-physics-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-plugin-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-plugin-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-ros2-control: 2.0.5-1 → 2.0.6-1
• ros-rolling-gz-ros2-control-dbgsym: 2.0.5-1 → 2.0.6-1
• ros-rolling-gz-ros2-control-demos: 2.0.5-1 → 2.0.6-1
• ros-rolling-gz-ros2-control-demos-dbgsym: 2.0.5-1 → 2.0.6-1
• ros-rolling-gz-sensors-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-sensors-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-sim-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-sim-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-transport-vendor: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-transport-vendor-dbgsym: 0.2.0-1 → 0.2.1-1
• ros-rolling-gz-utils-vendor: 0.2.1-1 → 0.2.2-1
• ros-rolling-gz-utils-vendor-dbgsym: 0.2.1-1 → 0.2.2-1
• ros-rolling-image-pipeline: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-proc: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-proc-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-publisher: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-publisher-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-rotate: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-rotate-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-view: 6.0.9-1 → 6.0.10-1
• ros-rolling-image-view-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-kitti-metrics-eval: 1.6.1-1 → 1.6.2-1
• ros-rolling-kitti-metrics-eval-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-launch: 3.7.1-1 → 3.8.0-1
• ros-rolling-launch-pytest: 3.7.1-1 → 3.8.0-1
• ros-rolling-launch-testing: 3.7.1-1 → 3.8.0-1
• ros-rolling-launch-testing-ament-cmake: 3.7.1-1 → 3.8.0-1
• ros-rolling-launch-xml: 3.7.1-1 → 3.8.0-1
• ros-rolling-launch-yaml: 3.7.1-1 → 3.8.0-1
• ros-rolling-mola: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-bridge-ros2: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-bridge-ros2-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-demos: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-imu-preintegration: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-imu-preintegration-dbgsym: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-input-euroc-dataset: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-euroc-dataset-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-kitti-dataset: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-kitti-dataset-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-kitti360-dataset: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-kitti360-dataset-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-mulran-dataset: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-mulran-dataset-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-paris-luco-dataset: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-paris-luco-dataset-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-rawlog: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-rawlog-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-rosbag2: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-input-rosbag2-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-kernel: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-kernel-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-launcher: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-launcher-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-lidar-odometry: 0.6.1-1 → 0.7.0-1
• ros-rolling-mola-lidar-odometry-dbgsym: 0.6.1-1 → 0.7.0-1
• ros-rolling-mola-metric-maps: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-metric-maps-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-msgs: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-msgs-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-pose-list: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-pose-list-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-relocalization: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-relocalization-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-state-estimation: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-state-estimation-simple: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-state-estimation-simple-dbgsym: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-state-estimation-smoother: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-state-estimation-smoother-dbgsym: 1.6.1-1 → 1.7.0-1
• ros-rolling-mola-traj-tools: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-traj-tools-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-viz: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-viz-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-yaml: 1.6.1-1 → 1.6.2-1
• ros-rolling-mola-yaml-dbgsym: 1.6.1-1 → 1.6.2-1
• ros-rolling-moveit: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-common: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-configs-utils: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-core: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-core-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-hybrid-planning: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-hybrid-planning-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-kinematics: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-kinematics-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-chomp: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-chomp-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-ompl: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-ompl-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-stomp: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-planners-stomp-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-plugins: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-py: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-py-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-resources-prbt-ikfast-manipulator-plugin: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-resources-prbt-moveit-config: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-resources-prbt-pg70-support: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-resources-prbt-support: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-benchmarks: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-benchmarks-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-control-interface: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-control-interface-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-move-group: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-move-group-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-occupancy-map-monitor: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-occupancy-map-monitor-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-perception: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-perception-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-planning: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-planning-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-planning-interface: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-planning-interface-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-robot-interaction: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-robot-interaction-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-tests: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-trajectory-cache: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-trajectory-cache-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-visualization: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-visualization-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-warehouse: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-ros-warehouse-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-runtime: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-app-plugins: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-app-plugins-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-assistant: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-assistant-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-controllers: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-controllers-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-core-plugins: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-core-plugins-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-framework: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-framework-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-srdf-plugins: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-setup-srdf-plugins-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-simple-controller-manager: 2.12.0-1 → 2.13.0-1
• ros-rolling-moveit-simple-controller-manager-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-mp2p-icp: 1.6.5-1 → 1.6.6-1
• ros-rolling-mp2p-icp-dbgsym: 1.6.5-1 → 1.6.6-1
• ros-rolling-pangolin: 0.9.1-2 → 0.9.3-1
• ros-rolling-pangolin-dbgsym: 0.9.1-2 → 0.9.3-1
• ros-rolling-pilz-industrial-motion-planner: 2.12.0-1 → 2.13.0-1
• ros-rolling-pilz-industrial-motion-planner-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-pilz-industrial-motion-planner-testutils: 2.12.0-1 → 2.13.0-1
• ros-rolling-pilz-industrial-motion-planner-testutils-dbgsym: 2.12.0-1 → 2.13.0-1
• ros-rolling-realtime-tools: 4.0.0-1 → 4.1.0-1
• ros-rolling-realtime-tools-dbgsym: 4.0.0-1 → 4.1.0-1
• ros-rolling-rmw: 7.6.0-1 → 7.8.0-1
• ros-rolling-rmw-connextdds: 0.25.0-1 → 1.0.0-1
• ros-rolling-rmw-connextdds-common: 0.25.0-1 → 1.0.0-1
• ros-rolling-rmw-connextdds-common-dbgsym: 0.25.0-1 → 1.0.0-1
• ros-rolling-rmw-connextdds-dbgsym: 0.25.0-1 → 1.0.0-1
• ros-rolling-rmw-cyclonedds-cpp: 3.2.0-1 → 4.0.0-1
• ros-rolling-rmw-cyclonedds-cpp-dbgsym: 3.2.0-1 → 4.0.0-1
• ros-rolling-rmw-dbgsym: 7.6.0-1 → 7.8.0-1
• ros-rolling-rmw-dds-common: 3.2.0-1 → 3.2.1-1
• ros-rolling-rmw-dds-common-dbgsym: 3.2.0-1 → 3.2.1-1
• ros-rolling-rmw-fastrtps-cpp: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-fastrtps-cpp-dbgsym: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-fastrtps-dynamic-cpp: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-fastrtps-dynamic-cpp-dbgsym: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-fastrtps-shared-cpp: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-fastrtps-shared-cpp-dbgsym: 9.2.0-1 → 9.3.0-1
• ros-rolling-rmw-implementation-cmake: 7.6.0-1 → 7.8.0-1
• ros-rolling-rmw-zenoh-cpp: 0.3.1-1 → 0.4.0-1
• ros-rolling-rmw-zenoh-cpp-dbgsym: 0.3.1-1 → 0.4.0-1
• ros-rolling-ros-gz: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-bridge: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-bridge-dbgsym: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-image: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-image-dbgsym: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-interfaces: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-interfaces-dbgsym: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-sim: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-sim-dbgsym: 2.1.4-1 → 2.1.5-1
• ros-rolling-ros-gz-sim-demos: 2.1.4-1 → 2.1.5-1
• ros-rolling-rosapi: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosapi-msgs: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosapi-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-library: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-msgs: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-server: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-suite: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-test-msgs: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosbridge-test-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
• ros-rolling-rosidl-dynamic-typesupport-fastrtps: 0.3.0-1 → 0.4.0-1
• ros-rolling-rosidl-dynamic-typesupport-fastrtps-dbgsym: 0.3.0-1 → 0.4.0-1
• ros-rolling-rti-connext-dds-cmake-module: 0.25.0-1 → 1.0.0-1
• ros-rolling-sdformat-vendor: 0.2.3-2 → 0.2.4-1
• ros-rolling-sdformat-vendor-dbgsym: 0.2.3-2 → 0.2.4-1
• ros-rolling-septentrio-gnss-driver: 1.4.1-1 → 1.4.2-1
• ros-rolling-septentrio-gnss-driver-dbgsym: 1.4.1-1 → 1.4.2-1
• ros-rolling-simple-launch: 1.10.1-1 → 1.11.0-1
• ros-rolling-stereo-image-proc: 6.0.9-1 → 6.0.10-1
• ros-rolling-stereo-image-proc-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-test-ros-gz-bridge: 2.1.4-1 → 2.1.5-1
• ros-rolling-topic-tools: 1.4.1-1 → 1.4.2-1
• ros-rolling-topic-tools-dbgsym: 1.4.1-1 → 1.4.2-1
• ros-rolling-topic-tools-interfaces: 1.4.1-1 → 1.4.2-1
• ros-rolling-topic-tools-interfaces-dbgsym: 1.4.1-1 → 1.4.2-1
• ros-rolling-tracetools-image-pipeline: 6.0.9-1 → 6.0.10-1
• ros-rolling-tracetools-image-pipeline-dbgsym: 6.0.9-1 → 6.0.10-1
• ros-rolling-turtlebot3-msgs: 2.2.1-4 → 2.3.0-1
• ros-rolling-turtlebot3-msgs-dbgsym: 2.2.1-4 → 2.3.0-1
• ros-rolling-ur-client-library: 1.6.0-1 → 1.7.1-1
• ros-rolling-ur-client-library-dbgsym: 1.6.0-1 → 1.7.1-1
• ros-rolling-webots-ros2: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-control: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-control-dbgsym: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-driver: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-driver-dbgsym: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-epuck: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-importer: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-mavic: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-msgs: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-msgs-dbgsym: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-tesla: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-tests: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-tiago: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-turtlebot: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-webots-ros2-universal-robot: 2023.1.3-1 → 2025.0.0-1
• ros-rolling-zenoh-cpp-vendor: 0.3.1-1 → 0.4.0-1
• ros-rolling-zenoh-cpp-vendor-dbgsym: 0.3.1-1 → 0.4.0-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
• Alejandro Hernandez
• Alejandro Hernandez Cordero
• Alejandro Hernández
• Alexander Gutenkunst
• Andrea Sorbini
• Automatika Robotics
• Bence Magyar
• Blake Anderson
• Brandon Ong
• Błażej Sowa
• Chittaranjan Srinivas Swaminathan
• Chris Bollinger
• Christian Henkel
• Cyberbotics
• David V. Lu!!
• Elevate Robotics
• Emerson Knapp
• Erik Boasson
• Felix Exner
• Geoffrey Biggs
• Henning Kayser
• Husarion
• Ivan Paunovic
• Jose Luis Blanco-Claraco
• Jose-Luis Blanco-Claraco
• Joseph Mirabel
• José Luis Blanco-Claraco
• Justin Carpentier
• Kimberly McGuire (Bitcraze AB)
• Max Krogius
• Michael Görner
• Miguel Company
• MoveIt Release Team
• Olivier Kermorgant
• Peter David Fagan
• Pyo
• Steven Lovegrove
• Tibor Dome
• Tim Clephas
• Vincent Rabaud
• Víctor Mayoral-Vilches
• Yadunund

3 posts - 2 participants

Read full topic