v0.1.8

Highlights

Version-aware TimescaleDB restore

Backups now record each database's source TimescaleDB extension version in the manifest. On restore, a database whose recorded version does not match this server's bundled TimescaleDB is skipped before any destructive step (no terminate / DROP / CREATE) — your live data is left untouched — and the restore exits non-zero with exact, copy-pasteable instructions to align the version and retry. When versions match, restore proceeds automatically as before. Legacy backups (no recorded version) and the PostgreSQL / MySQL / MariaDB / SQLite paths are unchanged.

Install robustness

• Shared libraries are always refreshed on installed machines, so an outdated common.sh can no longer cause runtime failures such as harden_secret_file: command not found. The refresh is best-effort — atomic, with a connect-timeout and fallback to the existing libraries — so offline and restricted-network installs are not regressed; local checkouts and the standalone bundles are untouched.
• Docker Compose v2 plugin is auto-installed when the Docker engine is present but the plugin is missing (e.g. the distro docker.io package), fixing docker compose v2 not found during installation.
• sqlite3 install is now genuinely best-effort during backup and no longer aborts the backup if the package cannot be installed.

Full Changelog: v0.1.7...v0.1.8