pub const API_MINOR: u32 = 10;Expand description
The integer MINOR of API_VERSION — see there. Bumped from 0 to 1 when params validation
became strict (#34); to 2 with the set_nickname verb + StatusResult.self_nickname (#37);
to 3 when allow/grant strings became STABLE principals — b64u:/eid:/roster names,
never nicknames (#38); to 4 with the set_app_metadata verb + PresencePeer.meta (#39);
to 5 with PeerReachability.meta — pairing-mode app metadata on the probe pong (#40);
to 6 with PeerInfo.principal — the peer’s eid: device principal on status (#41);
to 7 with PeerReachability.principal — the same on reachability rows (#42); to 8 with the
service_allow_grant/service_allow_revoke per-peer access verbs (#44); to 9 covering the
unregister_service (#50) / peer_services (#52) / Run env+cwd (#51) surface that shipped
in 0.10.1 without a bump, PLUS the set_relays live relay-set verb (#53); to 10 when
service_allow_revoke/peer_remove became IMMEDIATE — no verb shape changed, but their
observable contract did: a revoked principal’s next session is refused even on a connection it
already holds, and its live connections are severed. Previously both waited for the peer to
disconnect on its own, which is unbounded (#54). A consumer can guard on
api_minor >= 10 before telling a user that revocation has taken effect.