Version matrix
M0 contract traceability
Every public contract-bearing surface should identify the contract version it implements.
| Surface | Current M0 version | Status |
|---|---|---|
| Mesh contract | mesh-v2.0.0-m0 | Preferred contract: mesh-v2.0.0-m0 |
| OpenAPI | mesh-v1.0.0-m2 | Published as JSON and YAML |
| Mesh service | alloy-mesh-service:1.0.0-SNAPSHOT | Runtime gate requires the current supported contract. |
| TypeScript SDK | 0.2.0-m0 | Supports mesh-v2.0.0-m0 |
| JVM client | 0.1.0-m0 | Supports mesh-v2.0.0-m0 |
Compatibility registry
The deployed docs include the Mesh compatibility registry alongside the generated OpenAPI specs.
| Contract | Status | Servers | Clients | Lifecycle |
|---|---|---|---|---|
| mesh-v2.0.0-m0 | current | alloy-mesh-service:1.0.0-SNAPSHOT | alloy-mesh-client-jvm:0.2.0-m0, alloy-mesh-client-ts:0.2.0-m0 | Introduced 2026-08-06; deprecated null; removal null |