Skip to content
Migo

Support and Version Matrix

This page answers the two most practical questions on the vendor side: “which version am I integrating, and how does it relate to my platform”. Maturity assessment (“is it production-ready today”) is out of scope here — see Platform Selection. This page covers mechanical facts: series, artifact shape, and minimum requirements.

SDK Series and Semver

Section titled “SDK Series and Semver”
  • Version numbers follow Semantic Versioning; every change is recorded in the CHANGELOG (Keep a Changelog format). The current series is read from release/VERSION at the repository root — the developer-documentation version number is also derived from it (major.minor becomes docsSeries, single source of truth).
  • Documentation version = SDK version. Current stable content is served at /docs/, while the complete 0.9.7 release baseline is frozen at /docs/0.9/; the English equivalents are /docs/en/ and /docs/en/0.9/. When a future series ships, starlight-versions generates a new archive for the outgoing series and adds it to the version switcher; archives are not routine editing targets.
  • ABI status remains CANDIDATE: see ABI Compatibility — the struct-negotiation mechanism is in place and has been validated on both paths, but binary compatibility is not a contractual guarantee until the freeze announcement is made.

Platform × Artifact

Section titled “Platform × Artifact”
Platform Deliverable ABI Support Minimum Requirement
Android Static library + CMake package (find_package(migo)), Java AAR facade arm64-v8a, x86_64 minSdk 26 (see the android-sdk page and test-android-sdk-levels-contract.sh); on-device multi-touch requires the instrumentation APK path (one of the ABI freeze blockers)
OpenHarmony Static library, DevEco host project aarch64, x86_64 Target device per the OHOS target manifest; multi-touch validated only in the API 20 simulator — on-device regression is the host’s job
Windows migo.dll + rusty_v8.dll + headers, CMake target x64, arm64 Windows (with ANGLE/HWND); WinUI integration is the host’s responsibility
Linux host-kit toolchain + wayland/x11 platform headers + pkg-config/CMake x86_64 glibc only (musl/bionic: headers only, no runtime); official build sysroot and glibc lower bound: see the release manifest
Apple (iOS/macOS) SwiftPM: MigoAppleCore / MigoAppleRenderer (CI build artifacts) arm64, x86_64 (macOS) / arm64 (iOS) Placeholder lane; no on-device run records yet; macOS can attach the host’s own CAMetalLayer

Per-platform integration details are covered step by step in each quickstart; product-level trade-offs (“is it production-ready”) are covered in Platform Selection.

When to Re-read This Page

Section titled “When to Re-read This Page”
  • When a new series ships (e.g. 0.10): add a row to this page; the previous series’ documentation enters the archive. The specific upgrade guide for 0.10 is in Version Upgrades.
  • When ABI CANDIDATE status is lifted: the ABI section is rewritten in tandem with the ABI Compatibility status page.

See Also

Section titled “See Also”