Version Compatibility
MTE Relay follows semantic versioning. Within a major version, releases are strictly additive and backwards compatible.
The rule
Any v4 client works with any v4 server. You do not need to upgrade clients and servers in lockstep. Minor and patch releases never break compatibility inside the same major version.
Current v4 releases
| Component | Distribution | Current release |
|---|---|---|
| MTE Relay Server (MRS) | AWS / Azure marketplaces, on premise images | 4.7.0 |
| MTE API Relay (MAR) | AWS / Azure marketplaces, on premise images | 4.7.0 |
| Web JavaScript client | npm: mte-relay-browser-public-client | 4.5.2 |
| Android client | Maven | See Android guide |
| iOS client | Swift Package Manager | See iOS guide |
| Flutter client | SPM / CocoaPods | See Flutter guides |
| Blazor client | Package reference | See Blazor guide |
Upgrading
- Server images are tagged per release (for example
4.7.0). Upgrading a server is redeploying with the new tag; no client changes are required. - Features introduced mid major are marked in these docs with a badge, for example: Since 4.7.0. If you run an older minor, the badge tells you the minimum server version that supports the feature.
- Breaking changes only ever arrive with a new major version, which gets its own documentation set (selectable in the navbar version dropdown).