Coeval v0.2.0
This is the first Coeval release with a supported, persistent self-host baseline, versioned deployment bundle, and release pipeline.
Self-hosting
- Adds
deploy/self-host/compose.yamlfor Docker Compose, Coolify, and other Compose-capable control planes. - Publishes exact multi-architecture images for
linux/amd64andlinux/arm64:ghcr.io/luka-zivkovic/coeval-api:0.2.0ghcr.io/luka-zivkovic/coeval-web:0.2.0
- Pins PostgreSQL and keeps both application images on one exact Coeval version.
- Documents backup, restore, health-check, and explicit upgrade procedures.
Database and recovery contract
- Do not point v0.2.0 at a database previously started by v0.1.0 or another pre-release build. Coeval v0.2.0 freezes the first supported persistent
0001_baseline.sql; there is no supported in-place upgrade from the earlier development baseline or the historical0001–0055development chain. - Start v0.2.0 with a new PostgreSQL database. If an older database contains important data, keep it and its compatible application image intact; no automated conversion path is claimed by this release.
- From this release forward, later schema changes must use checksum-verified, append-only migrations with explicit compatibility and recovery notes.
- Before every future update, retain an off-host PostgreSQL backup plus the prior Compose definition and
.env, includingCOEVAL_AUTH_SECRET. - Never use
docker compose down -vas an update or recovery command.
The release pipeline verifies the complete test suite, publishes immutable exact-version and commit-SHA image tags, then boots the published Compose bundle and verifies /health before producing this release.
What's changed
- Beginner onboarding and first-Check workflow improvements.
- Conversational external-agent onboarding and persistent Settings access.
- Approved Coeval identity and logo.
- Supported self-host release and long-term upgrade path.
Full changelog: v0.1.0...v0.2.0