Migration Guides¶
What changed between Tempo versions, and what you have to do about it.
| Guide | Affects | Danger |
|---|---|---|
| v0.3.0 | TempoWorld transform, property and function-calling APIs | Two changes break silently at runtime |
| Sensor payloads, API v0.2.0 | Any client decoding lidar or depth data | labels decodes as garbage with no error |
| v0.1.0 | Plugin layout, module names, proto packages | Loud — things fail to build or resolve |
General advice¶
- Upgrade the client and server together. Tempo's proto packages carry the wire identity, so a client generated against one version is not guaranteed to talk to a server from another.
- Reinstall the whole client package, not just the
_pb2modules. The hand-written helper wrappers (TempoImageUtils,TempoLidarUtils) are not regenerated by proto codegen, so a partial upgrade leaves stale wrappers calling new stubs. - Watch for silent breaks. The changes flagged above compile and run — they just do the wrong thing. Grep for the affected calls rather than relying on the build to find them.