v0.3.6

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.

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.

v0.3.4

What's Changed

• Add public SDK transport types and packed consumer documentation gates by @burdettadam in #37

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

• Fix Actions release visibility and prepare client v0.3.3 by @burdettadam in #35
• Bound and diagnose owned draft visibility in release preflight by @burdettadam in #36

Full Changelog: v0.3.2...v0.3.3

v0.3.1

What's Changed

• Fix release archive license check and prepare client v0.3.1 by @burdettadam in #32

Full Changelog: v0.3.0...v0.3.1

v0.2.7

What's Changed

• chore(deps): bump actions/attest-build-provenance from 4.1.1 to 4.2.2 in the github-actions-dependencies group across 1 directory by @dependabot[bot] in #13
• release: prepare marty-cli v0.2.7 by @burdettadam in #19

Full Changelog: v0.2.6...v0.2.7

v0.2.6

What's Changed

• fix(api-core): initialize WASM under jsdom by @burdettadam in #17

Full Changelog: v0.2.5...v0.2.6

v0.2.5

What's Changed

• fix(api-core): initialize WASM in Vite browsers by @burdettadam in #16

Full Changelog: v0.2.4...v0.2.5

v0.2.4

What's Changed

• chore(deps): bump the github-actions-dependencies group across 1 directory with 2 updates by @dependabot[bot] in #7
• chore: refresh monthly Node toolchains by @github-actions[bot] in #8
• feat: port Marty CLI behavior to Rust by @burdettadam in #14
• fix: align API client with MIP 0.5.0 by @burdettadam in #15

New Contributors

• @github-actions[bot] made their first contribution in #8

Full Changelog: v0.2.3...v0.2.4

v0.2.3

What's Changed

• chore: consume MIP 0.4.1 by @burdettadam in #12

Full Changelog: v0.2.2...v0.2.3