Hi,
I am wondering why your ROS2 wrapper repository is not versioned with the semantic versioning anymore? For example 2025-10-13 version introduced many breaking changes due to topic name changes, but such thing is much harder to notice if semantic versioning is not used. We use many ZED X One cameras and such change without proper versioning/tagging is painful to maintain. It’s also less clear which SDK version is required for certain code version.
Best regards,
fgrcar
Hi @fgrcar
We apologise for the inconvenience, the robotics team was in Singapore for ROSCon 2025, and we are a bit in late with this development.
We have not yet tagged v5.1 because the porting to ZED SDK v5.1 is not yet completed, and not all the features provided by the ZED SDK v5.1 are available with the wrapper.
The final tag v5.1 of the ZED ROS2 Wrapper will be released as soon as the porting is completed, hopefully, before the end of the week.
The current version of the Wrapper in the master branch is compatible with v5.1.
The breaking change that we introduced was required to have coherent topic names when using Stereo and Monocular cameras together in hybrid configurations.
Thanks for the reply and explanation.
It wouldn’t hurt if also bugfix versions would be tagged as it’s not uncommon that some changes happen that require specific SDK version. In ideal world it would also be good to wait with the breaking changes until the major version update, at least the semantic versioning is instructing it that way. Anyway, I hope you improve this in the future. 
Best regards.
Normally, the tendency is not to introduce breaking changes unless we target a new ROS 2 LTS version that is no longer compatible with the previous.
As I said, this is a particular condition, and I do not think something similar will happen again soon.
The next breaking change will probably involve the release of the ZED SDK v6.0; in that case, we will probably modify the ZED ROS2 Wrapper components to transform them into Lifecycle nodes, for better control over their status, mostly when used with Nav2 or ROS Control nodes.