basaltd 0.9.0

What changed

This server release accompanies the Basalt 0.9.0 CLI and Obsidian plugin release. The server runtime is unchanged from 0.8.5. Its startup test now waits for the server to be serving before checking contention, avoiding a false failure between its two lock acquisitions.

MCP runs in the separately paired headless client, not in basaltd. The sync server continues to store encrypted content and does not receive the client's plaintext notes or decryption keys.

Upgrade

Protocol 7 and the on-disk format are unchanged. Existing 0.8.x clients remain compatible, and existing data and pairings are retained. No migration or re-pairing is required.

Use ghcr.io/waynehoover/basalt-sync:0.9.0, preferably pinned to its published digest, or the matching binary below. Stop the previous server cleanly and keep the existing data directory, ownership and configuration. The release provides Linux amd64/arm64 container images and Linux/macOS amd64/arm64 binaries.

There is no new server feature needed to enable MCP. Install the 0.9.0 CLI on a trusted host, pair a separate local vault, and follow the MCP guide.

Verification and limits

Release checks include server race tests, a backup/restore rehearsal, protocol integration tests and execution of both published container architectures. Process termination tests do not simulate power loss. Existing local-filesystem and trusted-device assumptions remain; network filesystems are unsupported.

Verify the downloaded files and their provenance:

shasum -a 256 -c SHA256SUMS
gh attestation verify basaltd-linux-amd64 --repo waynehoover/basalt-sync