Repository navigation
What's Changed
- fix: return native transport initialization errors and qualify CA prerequisites by @burdettadam in #39
Full Changelog: v0.3.5...v0.3.6
Runtime prerequisites and qualification
Native Linux GNU binaries require compatible glibc and a readable OS CA certificate store. Install the distribution's ca-certificates package from its approved repository before running HTTP commands, including commands against an HTTP API URL. Private CAs belong in the OS trust policy. v0.3.6 reports HTTP transport initialization failure as an error with a CA-store hint; TLS verification remains enabled.
The JavaScript/WASM SDK requires Node 24 or a compatible browser host, which supplies its own transport trust policy. GitHub release tarballs are the install channel; npm registry publication is not enabled. The client package version is separate from its MIP 0.5.0 wire version and server release compatibility.
Fresh installed published packages passed local Windows x64 and Ubuntu 24.04 x64 consumer checks with Node 24.15.0: six public CLI setup/key-management HTTP requests, SDK/WASM transport and executable documentation. Strict Node/browser SDK type consumers also passed. Ubuntu used its signed distribution ca-certificates package; the runtime was nonroot, read-only and offline, with no external certificate-bundle mount. The actual published Linux binary also passed graceful missing-CA failure in the bare pinned Ubuntu image. Other native hosts have release-producer setup/entry-point probes; an independent fresh local runtime is not claimed for every host.
These checks use HTTP fixtures. They do not qualify a deployed Marty gateway, initial operator bootstrap, an entire console-free business lifecycle, or every server/client combination. Verify SHA256SUMS and GitHub build attestations against tag v0.3.6 and source ac217199afcff451e36f7c244b6e523817696d7e before use.
