Know exactly what v0.1.5 supports.

v0.1.5 is the current stable public-preview release. The v0.1.x line now includes Gantry peer clustering and propagation plus SQLite Raft replication alongside the original single-node and PostgreSQL surfaces.

Supported surfaces

• Linux and macOS on amd64 and arm64, plus Windows on amd64 and arm64.
• Standalone operation with an owned local SQLite database or PostgreSQL 16, 17 or 18.
• Gantry peer clustering for authenticated node pairing, health/status aggregation, comparison and controlled configuration propagation.
• Optional SQLite Raft replication for collection definitions and records, with explicit voter membership, quorum writes, follower forwarding, snapshots and recovery.
• Versioned HTTP contracts under /api/v1, /admin/v1 and /system.
• Application users, scoped service identities, access rules, records, files, SSE, jobs, audit, webhooks, Lambda targets, backups and offline restore.
• Cross-provider migration between SQLite and PostgreSQL, with provider-specific backup and restore procedures.
• Checksum-verified archives, user installation, executable update and explicit rollback.

Outside the v0.1.x contract

• Multiple Trestle processes sharing one database or SQLite on a shared/network filesystem; clustered SQLite nodes each own their local database and Raft state.
• PostgreSQL Raft replication; the replicated collection/record surface is SQLite-only and fails closed if configured with PostgreSQL.
• Automatic replication of files, credentials, sessions, jobs, webhook/function execution, audit/events or other external side effects.
• Managed/serverless PostgreSQL topologies beyond the tested single-process ownership model.
• Automatic database downgrade during executable rollback.
• Direct application-user file delivery through collection rules.
• Target-aware relation foreign keys or automatic relation expansion.
• Outbound verification email and self-service password recovery.
• An official container image or managed service.

Release verification

v0.1.2 was released from reviewed commit 91c6441 (release workflow run 33818618083: six archives plus SHA256SUMS, checksum and provenance verification, stable-public-preview body) and passed the permanent read-only release-verification workflow (33818989370: exact seven-asset set, every checksum, constrained gh attestation verify on every archive, body wording). v0.1.1 was the prior patch on the same contract, and v0.1.0 established the initial contract; both were verified through their own release and read-only verification runs.

The PostgreSQL readiness contract is machine-readable at docs/postgres/postgres-readiness.json in the application repository and enforced by TestPostgresReadinessContract, which also probes a real server when configured. One command runs the reproducible PostgreSQL gate against a real server:

./scripts/test-postgres-gate.sh

The gate provisions a disposable local instance when no TRESTLE_TEST_POSTGRES_URL is supplied, never prints connection credentials, and runs the contract probe, the full provider-parameterized suite and the race-enabled provider suite. The PostgreSQL contract and the pre-release position are recorded per checkpoint in PREVIEW-CHECKPOINTS.md; automated, simulated, local real-service and CI evidence are labelled accurately.