Release notes and compatibility
Use the documentation version matching the running Obot release. Next describes unreleased work and can include capabilities absent from released images.
Release notes are maintained in Obot's GitHub releases. Review the notes for each release involved in an upgrade, alongside Upgrades and rollback.
| Compatibility area | Reference |
|---|---|
| Provider routes, request formats, and client caveats | LLM API compatibility |
| Local client inventory and enforcement coverage | Device inventory and enforcement |
| Legacy MCP endpoints and vMCP transition | vMCP migration |
| Git catalog formats and vMCP synchronization limits | Git-backed configuration |
| Edition and feature availability | Obot Editions |
A documentation reorganization does not change release compatibility. Keep existing endpoints during the documented transition and test representative clients before deploying a new server version.