MEHS / Knowledge base

Changelog

Notable MEHS changes and compatibility guidance. Package versions follow semantic versioning but do not imply a finalized or interoperable wire protocol. Historical notes describe their release, not today's platform status.

The live release archive may contain newer packages than the documented notes below. Download metadata does not include change descriptions; no undocumented release changes are inferred here.

Unreleased

Changed

Fixed

Unreleased behavior is not a guarantee for currently downloaded packages. In particular, initial-connect retry behavior differs from the published CLI contract.

0.9.2 - 2026-10-22

Beta pre-release. Use the 0.9.2 client and server together; mixed patch releases are not certified.

Added

Changed

Fixed

Compatibility and upgrade

Wire migration checklist

For incompatible releases, record old/new frame versions and ALPN/profile identifiers; exact supported and unsupported client/server pairs; failure stage (authorization, TLS/ALPN, or decode); upgrade order and rollback constraints; and effects on active sessions, flows, and reconnects.

0.9.1 - 2026-10-19

0.9.0 - 2026-10-18

Added

Changed

Wire-incompatible with 0.8.x: probes require a 0.9.0 server; update clients and server together. Server max_connections (default 32) counts every link of every client.

0.8.1 - 2026-10-18

Added

Fixed

Closed-flow accounting, per-flow buffers, carrier keepalive, frame-size/unopened-flow crashes, and asynchronous task failure handling.

Changed

The package version became 0.8.1 after an earlier 1.0.0 label; the wire protocol remains evolving.

1.0.0 - 2026-10-16 (historical label)

Added

Fixed

Security

Mandatory TLS 1.3 certificate validation; session-to-transport binding; resource bounds for connections, frames and buffers; no sensitive-data logging.

Roadmap and known limitations

Open gaps are not dated commitments: stable wire interoperability, full device/platform lifecycle validation, broader monitoring beyond status/metrics, durable multi-process credential/session storage, and independent security assurance. Default stores are in-memory; optional file stores are single-process and need deployment-specific protection.

Android hosts must configure VPN descriptors, addresses, routes, and DNS. Hosts must pause probing/new connections during sleep, validate health before resuming, and react to network changes. Later releases add iOS integration; consult the current support matrix, platform lifecycle guide, and security policy.