# Releases, Versioning, and Public API claim of ros-controls

**URL:** <https://discourse.openrobotics.org/t/releases-versioning-and-public-api-claim-of-ros-controls/50388>\
**Category:** ros-controls Announcements and News\
**Tags:** release\
**Created:** [October 2, 2025, 6:35pm UTC](https://discourse.openrobotics.org/t/releases-versioning-and-public-api-claim-of-ros-controls/50388 "2025-10-02T18:35:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![christophfroehlich](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophfroehlich/32/31526_2.png) [@christophfroehlich](https://discourse.openrobotics.org/u/christophfroehlich)\
**Post date:** [October 6, 2025, 6:17pm UTC](https://discourse.openrobotics.org/t/releases-versioning-and-public-api-claim-of-ros-controls/50388/3 "2025-10-06T18:17:24Z")

</div>

> [@christophfroehlich](#):
>
> We don’t guarantee ABI stability

We have discussed this a bit more in detail in the linked section:

> - ABI of plugins may change at every release, i.e., also within a **stable ros2\_control release**. Plugins built by the buildfarm will still be loaded by pluginlib’s class loader, but code linking against the exported libraries will break.
> 
> - For non-plugin code, ABI breaks within a **stable ros2\_control release** are less likely but still unavoidable to fix code, which is critical regarding safety aspects of robot control.

---

_[View the full topic](https://discourse.openrobotics.org/t/releases-versioning-and-public-api-claim-of-ros-controls/50388)._