v0.3.5

What's Changed

• Fix public setup requests and prepare client v0.3.5 by @burdettadam in #38

Full Changelog: v0.3.4...v0.3.5

Runtime prerequisites and qualification

Native Linux GNU binaries require compatible glibc and a readable OS CA certificate store. On minimal Ubuntu installations, install ca-certificates from the approved OS repository before running HTTP commands, including commands against an HTTP API URL. Manage private CAs through the OS trust policy; do not disable TLS verification.

Known v0.3.5 limitation: if the certificate store is absent, native HTTP transport initialization can panic. --version still works and does not establish HTTP readiness. v0.3.6 fixes this initialization panic and reports the CA-store prerequisite as an error. A readable certificate store is still required for native HTTP commands. Existing v0.3.5 binaries and package assets are unchanged.

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.

Local fresh-package consumer checks passed on Windows x64 and Ubuntu 24.04 x64 with an explicit public CA bundle, using Node 24.15.0. They cover six CLI setup/key-management HTTP requests, SDK/WASM transport and executable documentation; strict Node/browser SDK type consumers also passed. These fixture checks do not qualify a deployed gateway, an entire console-free lifecycle, every native host, or an installation without the prerequisites above. Verify downloaded checksums and GitHub build attestations against this release's exact source before use.